From: Stefan Monnier <monnier@iro.umontreal.ca>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: Harald Maier <harald@maierh.de>, 2375@emacsbugs.donarmstrong.com
Subject: bug#2375: 23.0.90; ^ in gnus summary buffer does not work in the nextstep build
Date: Thu, 26 Feb 2009 10:21:11 -0500 [thread overview]
Message-ID: <jwvd4d5dy6v.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <wlocwqxdvc.wl%mituharu@math.s.chiba-u.ac.jp> (YAMAMOTO Mitsuharu's message of "Thu, 26 Feb 2009 09:04:23 +0900")
>> I get the impression that it ends up behaving like the current
>> ns-win.el code (i.e. nothing is run after ^, but the Gnus command is
>> called after ^+SPC), except that it displays a "^" in the Gnus
>> buffer rather than signalling an error. Is that right?
> That's right. But I don't think the difference is so unimportant with
> respect to the current issue.
I never use dead keys like those, so I wouldn't know [a US keyboard plus
a compose key is all I need, plus the TeX input method, of course ;-)].
But I'll happily believe you.
It still leaves open the question of whether it would be desirable to
shortcut this so that pressing ^ in the Gnus summary immediately calls
the Gnus command, without having to press a subsequent SPC.
> Also, the difference in the code length shows how the Cocoa/GNUstep
> port oversimplifies the whole text input processing: it doesn't
> respect attributes in the marked text (which corresponds to text
> properties) or the selected range value.
I don't know what is "the marked text" nor what is "the selected range
value".
Stefan
next prev parent reply other threads:[~2009-02-26 15:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-18 18:27 bug#2375: 23.0.90; ^ in gnus summary buffer does not work in the nextstep build Harald Maier
2009-02-18 21:15 ` David Engster
2009-02-18 23:51 ` Stefan Monnier
2009-02-19 12:35 ` David Engster
2009-02-19 18:29 ` Stefan Monnier
2009-02-20 3:46 ` Harald Maier
2009-02-20 13:03 ` David Engster
2009-02-20 15:18 ` Stefan Monnier
2009-02-20 15:41 ` David Engster
2009-02-20 21:14 ` Stefan Monnier
2009-02-21 0:45 ` David Engster
2009-02-21 4:56 ` Harald Maier
2009-02-21 6:38 ` YAMAMOTO Mitsuharu
2009-02-21 9:30 ` Harald Maier
2009-02-22 1:39 ` YAMAMOTO Mitsuharu
2009-02-24 5:00 ` Harald Maier
2009-02-24 5:09 ` YAMAMOTO Mitsuharu
2009-02-25 16:25 ` Stefan Monnier
2009-02-26 0:04 ` YAMAMOTO Mitsuharu
2009-02-26 15:21 ` Stefan Monnier [this message]
2009-02-27 0:09 ` YAMAMOTO Mitsuharu
2009-03-09 13:25 ` Stefan Monnier
2009-03-10 0:05 ` YAMAMOTO Mitsuharu
2009-03-10 17:18 ` Stefan Monnier
2015-02-13 7:18 ` Lars Ingebrigtsen
2016-01-21 23:31 ` Alan Third
2009-02-26 16:49 ` David Engster
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=jwvd4d5dy6v.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=2375@emacsbugs.donarmstrong.com \
--cc=harald@maierh.de \
--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.