July 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Karl M. Hegbloom

I have several of my menus renamed like `%_File' and keys bound so that I can use `A-f' to get the file menu. When I push `A-f' then down arrow, I get an error message: Signaling: (wrong-type-argument characterp "Open...") I have NOT tried to investigate; I'll make a todo entry and just report it to yous for now.

1 participants
0 comments

Re: vc-revert-buffer1 sacrifices fontification preserving minor modes 26 years, 1 month

SL Baur

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: > Raymond Toy <toy(a)rtp.ericsson.se> writes: >> No, it's not Window NT native. I've seen exactly the same things >> (except with vc-cc) on Solaris. This happened right after some >> changes that were made in revert-buffer or something like that. I >> vaguely remember someone complaining that font-lock appeared to get >> run twice on revert-buffer. That would be me. >> Now it does't even get run once. :-( This isn't true. I revert buffers every day (usually ChangeLogs) and they get re-font-locked. > Can one of you guess step through that code and see where the > font-locking gets lost? Yes, please do this. The code that handles buffer mode initialization is extremely complex and I wouldn't be surprised if you are doing something subtle in vc.el to break it. If someone wishes to take on a smallish project that we will love you for years for doing, cleaning up buffer initialization is the project. ... > I see what you mean now. I think you mean this stuff from font-lock.el > ;; If the buffer is about to be reverted, it won't be fontified afterward. > (defun font-lock-revert-setup () > (setq font-lock-fontified nil)) > ;; If the buffer has just been reverted, normally that turns off > ;; Font Lock mode. So turn the mode back on if necessary. > ;; sb 1999-03-03 -- The above comment no longer appears to be operative as > ;; the first call to normal-mode *will* restore the font-lock state and > ;; this call forces a second font-locking to occur when reverting a buffer, > ;; which is wasteful at best. > ;(defalias 'font-lock-revert-cleanup 'turn-on-font-lock) > (defun font-lock-revert-cleanup ()) > a. Does undoing Steve's change help for your guys? Undoing my patch is not the correct thing to do, but it would be interesting to see if it has any effect. Once it is undone, also try doing a `M-x revert-buffer' on a large ChangeLog file. > b. Why _does_ the font-lock-ing work for me? I am using lazy-shot.el, > are you? Because normal-mode restores the font lock state. > P.S. I am using lazy-shot.el that sim I am using fast-lock.

1 participants
0 comments

`revert-buffer' is broken. 26 years, 1 month

Karl M. Hegbloom

I'm seeing double after a CVS update. The file is inserted rather than reverted.

1 participants
0 comments

Re: maybe a menubar bug in 21.1.4 26 years, 1 month

SL Baur

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes in xemacs-beta(a)xemacs.org: > Jeff Miller <jmiller(a)smart.net> writes: >> >> has anyone else seen this or even begin to have a clue why? >> > Maybe some issue with Motif vs non-Motif? None of the relevant code is guarded with anything remotely that. I believe that Jeff's recommended fix is the correct one.

2 participants
1 comments

Re: GNU Emacs new isearch feature 26 years, 1 month

Hrvoje Niksic

Darryl Okahata <darrylo(a)sr.hp.com> writes: > + ;; Bob's code was modified to use extents instead of overlays. Cool. Now if only it used itimers instead of timer.el so it can be used... itimer.el is always available in XEmacs, timer.el is not.

1 participants
0 comments

Re: GNU Emacs new isearch feature 26 years, 1 month

William M. Perry

Darryl Okahata <darrylo(a)sr.hp.com> writes: > I wrote: > > > The following just appeared via gnu-emacs-sources. It looks > > useful; anyone want to try adding this feature to XEmacs (if someone > > isn't already doing so)? > > Well, thanks to Jan Vroonhof, who pointed out that the XEmacs > isearch-mode.el isn't all that different from GNU Emacs' isearch.el, I > took a stab at porting this, and it wasn't very hard. Patch follows. > I haven't cc'd xemacs-patches, as I'd like people to try this out, and > see what they think. If everything's fine, I'll send it to > xemacs-patches next week. > > The patch is relative to the 21.1.4 isearch-mode.el. Works great here on XEmacs 21.2.18 - just a few offsets/fuzzes when patching. -bp

1 participants
0 comments

GNU Emacs new isearch feature 26 years, 1 month

Darryl Okahata

Just FYI, The following just appeared via gnu-emacs-sources. It looks useful; anyone want to try adding this feature to XEmacs (if someone isn't already doing so)? -- Darryl Okahata darrylo(a)sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.

1 participants
1 comments

Re: Image lib 26 years, 1 month

William M. Perry

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Charles G Waldman <cgw(a)fnal.gov> writes: > > > =?UNKNOWN?Q?Bj=F6rn?= Torkelsson writes: > > > > > Probably been discussed before, but why not Imlib? > > > > > > http://www.labs.redhat.com/imlib/tut/ > > > (to be http://www.rasterman.com/imlib/) > > > > Have you ever tried reading any of "rasterman"'s code? > > Or, even worse, using the programs that try to make use of his libraries? > Absolutely horrible. Not to mention that I cannot seem to find any API for loading images from data already in memory. Those who remember the ImageMagick integration I did, it was _painful_ to write every single image out to disk to a temp file and then read it back in. ImageMagick has the same features as ImLib, but it just wasn't worth it. -Bill P.

1 participants
0 comments

Re: Image lib 26 years, 1 month

Hrvoje Niksic

Charles G Waldman <cgw(a)fnal.gov> writes: > =?UNKNOWN?Q?Bj=F6rn?= Torkelsson writes: > > > Probably been discussed before, but why not Imlib? > > > > http://www.labs.redhat.com/imlib/tut/ > > (to be http://www.rasterman.com/imlib/) > > Have you ever tried reading any of "rasterman"'s code? Or, even worse, using the programs that try to make use of his libraries? Absolutely horrible.

1 participants
0 comments

Re: vc-revert-buffer1 sacrifices fontification preserving minor modes 26 years, 1 month

Raymond Toy

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> ;; If the buffer is about to be reverted, it won't be fontified afterward. Jan> (defun font-lock-revert-setup () Jan> (setq font-lock-fontified nil)) Jan> ;; If the buffer has just been reverted, normally that turns off Jan> ;; Font Lock mode. So turn the mode back on if necessary. Jan> ;; sb 1999-03-03 -- The above comment no longer appears to be operative as Jan> ;; the first call to normal-mode *will* restore the font-lock state and Jan> ;; this call forces a second font-locking to occur when reverting a buffer, Jan> ;; which is wasteful at best. Jan> ;(defalias 'font-lock-revert-cleanup 'turn-on-font-lock) Jan> (defun font-lock-revert-cleanup ()) Jan> a. Does undoing Steve's change help for your guys? Jan> b. Why _does_ the font-lock-ing work for me? I am using lazy-shot.el, Jan> are you? I'll give this a try soon. The problem is that sometimes font-lock goes away and sometimes it doesn't, and when it does goes away, I'm busy doing something else (real code!) so I don't bother to find out why. There does seem to be some correlation between the buffer size, though. Large buffers don't seem to get font-lock'ed again, but this is pure speculation. Jan> P.S. I am using lazy-shot.el that sim What? You mean Simon's version? I'm also using lazy-shot that comes in the sumo packages. Ray

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 July 1999