From: Adrian Robert <adrian.b.robert@gmail.com>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: Re: Nextstep manual merge
Date: Fri, 14 Nov 2008 22:18:46 -0500 [thread overview]
Message-ID: <5CBB6F91-FD13-4BE9-AEB8-77605FCC7E1D@gmail.com> (raw)
In-Reply-To: <wlk5b5vjax.wl%mituharu@math.s.chiba-u.ac.jp>
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.
prev parent reply other threads:[~2008-11-15 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 20:50 Nextstep manual merge Chong Yidong
2008-11-15 2:01 ` YAMAMOTO Mitsuharu
2008-11-15 3:18 ` Adrian Robert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5CBB6F91-FD13-4BE9-AEB8-77605FCC7E1D@gmail.com \
--to=adrian.b.robert@gmail.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=mituharu@math.s.chiba-u.ac.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.