September 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: fix for redisplay! 26 years, 7 months

Hrvoje Niksic

Andy Piper <andyp(a)parallax.co.uk> writes: > At 19:04 10/09/98 +0200, Hrvoje Niksic wrote: > >The redisplay rewrite is not alive, because Joel's company quit the > >project. There was an explanatory message to this list some time ago. > >However, his ideas are still good ones (or so it would seem to me), > >and rewriting the redisplay should be an interesting project. > > My $0.02 - I don't think we should ever do this unless we have > someone … [View More]

1 participants
0 comments

Re: Text properties slow down XEmacs 26 years, 7 months

Jan Vroonhof

Ben Wing <ben(a)666.com> "says": > The major time is not is not spent in creating extents but in > mapextent That is not the point: Major parts of the time are spent in creating 'text-properties'. The problem is that because the fact that this is non using _non-overlapping_ extents this involves doing a map-extents over all extents overlaying a region and that is about the slowest operations possible on extents. I am suggesting that some representation (of font-lock info or of … [View More]

2 participants
1 comments

Re: Need internal help please (dynamic loading support) 26 years, 7 months

Karl M. Hegbloom

>>>>> "William" == William M Perry <wmperry(a)aventail.com> writes: William> Do all platforms have the idea of an 'initialization' William> function for dynamic libraries? I know most elf systems William> do with _init and _fini, and windows has DllMain. It William> would be nice to just hook into that for doing the William> DEFSUBR() and things instead of having the somewhat William> arbitrary emacs_initializate function name. … [View More]

1 participants
0 comments

Re: [Various] [bug] XEmacs and gpm: SIGTSTP resignalling loop? 26 years, 7 months

Karl M. Hegbloom

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: >> I do not have enough programming experience to debug and fix >> the problem myself. Jan> I am afraid the only way to solve this is running XEmacs (and Jan> libgpm) under a debugger and look at what happens. Even Jan> without much pogramming experience that should be doable. I can try. I'll write on my todo board. >> I assume you work with current gpm (1.… [View More]14) otherwise all bets >> are off. Jan> Karl, did you? Debian hamm seems to have 1.13. I downloaded and tried 1.14, and the bug is still present. >> If there is indeed a conflict, it is not a problem with gpm: we >> really do it extra-extra clean way, calling back the original >> handler if there is any. A conflict is possible (likely) >> however if the app opens the gpm connection first and _then_ >> installs its own SIGTSTP handler, overwriting ours. If that is >> the problem, merely changing the order of initialisations >> should help. Jan> As far as grep can see XEmacs does not install its own Jan> SIGTSTP handler at all. Basically, all it does is send Jan> SIGTSTP to its whole program group if M-x suspend-emacs is Jan> called. That's what I thought. >> unless you can/want to modify Emacs internals, _and_ can find >> the one very special place in in the Emacs code where to call >> GPM_DRAWPOINTER from, the redisplay will clobber the pointer >> again. Jan> That will be at the end of the redisplay code, that should Jan> not be too difficult. Uhhhmmm... where's that? I began trying to read the XEmacs sources, and found myself in way over my head. Now I can understand much of `siod', and have some reading underway that should help me understand more... At some point I'll try and read XEmacs again. >> find that one special place, so I had the pointer visible >> through drags. I am almost sure that piece of code is >> different for XEmacs. Jan> I don't think it is that different. >> That said, I once added gpm support to GNU Emacs the dirty way >> (the way XEmacs seems to do it now, judging by your info) Jan> I find the current way gpm is implemented (114 lines of C Jan> code, including comments and whitespace) in XEmacs very Jan> clean. It does not involve running another subprocess from Jan> lisp nor does it involve manufacturing events from lisp Jan> code. The latter is only possible as of Jan> 21.0 anyway and is very tricky to get right. I wonder if doing it with a subprocess would work better though... [View Less]

1 participants
0 comments

Re: Bug: png files at cvs.xemacs.org 26 years, 7 months

SL Baur

Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes in xemacs-beta(a)xemacs.org: ... > I think that running 'cvs admin -kb' on each of the *.png files ought to > solve the problem. How strange, I thought I did that. Out of curiosity, do the PNGs in the 21.2 branch work?

4 participants
3 comments

Printing from XEmacs in NT4.0 26 years, 7 months

claudia.yastremiz＠barclayscapital.com

I am really looking forward to the release of 21.0 to use on my NT box. Therefore I jumped at the chance to download the binaries of XEmacs 21.0 b56 for MSWindows that Fabrice Popineau put somewhere on the net, and seems to work (very basic things) in NT4.0sp3, except for efs, that works for a bit and then hangs (the same happened on Solaris 2.5.1 with XEmacs 20.4, so I am not overly concerned about that). I am not sure about the problems with graphics support, since I have not used graphics … [View More]

3 participants
2 comments

Font lock (Was: Re: Text properties slow down XEmacs) 26 years, 7 months

Karl M. Hegbloom

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> The big question is: can font-lock.el be improved wihtout Jan> changing the interface to programs too much. Have yous seen the `scheme-lock.el' thing that I did? Please have a look; it's very short, only a couple screenfuls. It lets you set the font lock keywords and highlighting expressions using the customize interface, and the changes take effect immediately. If C mode had that, it … [View More]

1 participants
0 comments

a couple package-ui comments 26 years, 7 months

Greg Klanderman

first, this is amazingly cool, thanks, Darryl! unfortunately there is a checksum mismatch and it's not totally working, but it looks excellent. a couple suggestions for enhancements: * it'd be nice to force the user to specify a package-get-base.el file when started (with read-file-name) and give them a suitable default (efs path to xemacs,org). * also make them specify where to install the packages. package-get has an install-dir argument. don't surprise me... * it'd be nice … [View More]

1 participants
0 comments

Re: Elisp security checks? 26 years, 7 months

Hrvoje Niksic

karlheg(a)inetarena.com (Karl M. Hegbloom) writes: > Would it be useful for XEmacs to warn if it finds lisp that is > world or group writeable? Only as much as it would be useful for any other interpreter (such as a shell) to warn against world-writable stuff. Which is to say, not really. As with any other interpreter, you should know what you are doing when you load Lisp files from XEmacs. It would perhaps make sense to check the world-writability of `.emacs', which is loaded *… [View More]

1 participants
0 comments

Re: Visual bell too loud 26 years, 7 months

Karl M. Hegbloom

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> It would also be a good idea to implement something a la Hrvoje> FSFmacs `ring-bell-function', only perhaps as a console Hrvoje> method... Neat idea, I think. It would be possible to write a function that tells the window manager to do something interesting with the frame. It would be fun with `scwm' or `gwm'. :-) In the same vein, it would be good to be able to set an arbitrary … [View More]

1 participants
0 comments

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta September 1998