* Nextstep manual merge
@ 2008-11-14 20:50 Chong Yidong
2008-11-15 2:01 ` YAMAMOTO Mitsuharu
0 siblings, 1 reply; 3+ messages in thread
From: Chong Yidong @ 2008-11-14 20:50 UTC (permalink / raw
To: Adrian Robert; +Cc: emacs-devel
I've merged the Nextstep manual into macos.texi; please take a look, and
let me know if there are any problems.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Nextstep manual merge
2008-11-14 20:50 Nextstep manual merge Chong Yidong
@ 2008-11-15 2:01 ` YAMAMOTO Mitsuharu
2008-11-15 3:18 ` Adrian Robert
0 siblings, 1 reply; 3+ messages in thread
From: YAMAMOTO Mitsuharu @ 2008-11-15 2:01 UTC (permalink / raw
To: Chong Yidong; +Cc: Adrian Robert, emacs-devel
>>>>> On Fri, 14 Nov 2008 15:50:49 -0500, Chong Yidong <cyd@stupidchicken.com> said:
> I've merged the Nextstep manual into macos.texi; please take a look,
> and let me know if there are any problems.
What is the plan for "proper C-g handling" for the Cocoa/GNUstep port
before the Emacs 23.1 pretest? I think it is the most fundamental and
crucial functionality that the current implementation is missing.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Nextstep manual merge
2008-11-15 2:01 ` YAMAMOTO Mitsuharu
@ 2008-11-15 3:18 ` Adrian Robert
0 siblings, 0 replies; 3+ messages in thread
From: Adrian Robert @ 2008-11-15 3:18 UTC (permalink / raw
To: YAMAMOTO Mitsuharu; +Cc: Chong Yidong, emacs-devel
On Nov 14, 2008, at 9:01 PM, YAMAMOTO Mitsuharu wrote:
>>>>>> On Fri, 14 Nov 2008 15:50:49 -0500, Chong Yidong <cyd@stupidchicken.com
>>>>>> > said:
>
>> I've merged the Nextstep manual into macos.texi; please take a look,
>> and let me know if there are any problems.
>
> What is the plan for "proper C-g handling" for the Cocoa/GNUstep port
> before the Emacs 23.1 pretest? I think it is the most fundamental and
> crucial functionality that the current implementation is missing.
Three things I'm aware of need to be done:
1) complete removal of all Feval() calls in bad places as discussed
earlier on this list
2) go through the code comparing nsterm and macterm input handling to
make sure all ctrl-g related processing is similar
3) make sure that some sort of interrupt mechanism is in place to pick
up ctrl-g events when emacs core is busy processing and does not make
any input requests to the NS code (colored spinning disk shown in gui)
(1) is straightforward by using custom 'nonascii-keystroke' events,
except for the case of input-method handling when in isearch mode,
where passing such an event breaks out of the isearch entry. (2) is
more or less done, or was at one point. I did some experimentation
for (3) a while ago but failed, and some investigation is needed.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-11-15 3:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-11-14 20:50 Nextstep manual merge Chong Yidong
2008-11-15 2:01 ` YAMAMOTO Mitsuharu
2008-11-15 3:18 ` Adrian Robert
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.