[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [address@hidden: Re: [Preview-latex-devel] CVS-1.42; scale function]
From: |
David Kastrup |
Subject: |
Re: [address@hidden: Re: [Preview-latex-devel] CVS-1.42; scale function] |
Date: |
10 Nov 2001 00:45:32 +0100 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 |
>>>>> "Stefan" == Stefan Monnier <monnier+gnu.emacs.bug/news/@RUM.cs.yale.edu>
>>>>> writes:
Stefan> Indeed, reproducing this would be all too painful. We
Stefan> could maybe turn-off the minor-mode, put the event back on
Stefan> the unread-event queue, return and turn the minor-mode
Stefan> back on after the next command, but just thinking about
Stefan> makes me sick. And I'm not even sure it would do the
Stefan> right thing.
Several interface suggestions for telling the event loop to keep
retrying:
a) augment (interactive) codes with letters indicating the return
value of a function called interactively should not be ignored.
One could then have a letter for each of the following and more:
* the function returns an event that should be interpreted next.
* the function returns an event that should be passed onto the next
stage of interpretation (keymap lookup whatever). That's what we
would want here.
* the function returns a string that should be displayed in the echo
area, or inserted into the current buffer if the function was called
with a prefix argument. Actually, one could make this work for
arbitrary objects permissable to princ.
In all of these cases it would probably make sense if nothing happened
in case a function returned nil.
b) have a possibility to push back an event and tell the event loop to
interpret it in the next context. Probably a particular throw with
the event as a parameter would be good for that.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Email: David.Kastrup@t-online.de
Re: [address@hidden: Re: [Preview-latex-devel] CVS-1.42; scale function], Stefan Monnier, 2001/11/07