From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: zap-to-char too raw, or document
Date: Mon, 18 Jul 2011 22:39:19 +0900 [thread overview]
Message-ID: <87hb6jso6w.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <87mxgdwd1u.fsf@fencepost.gnu.org>
David Kastrup writes:
> When I answer a y/n style question, I would not want to have a
> latin-1-postfix input method waiting in order to figure out whether I
> want to adorn my n with a ~ in order to get ñ.
Emacs methods won't "be waiting"; they're buffer-, including
minibuffer-, specific. You will have to turn on the input method
explicitly. (At least, you would in XEmacs, I'm not 100% sure Emacs
works precisely the same way here.)
However, on second thought I'm not sure what the use case for a single
character via input method is, vs a one-character string via input
method. As you point out, it's a big deal to type even one extra
keystroke in a y-or-n-p context, but it's hardly a big deal to type
one extra RET after typing something like "C-\ i t i SPC SPC RET" to
get U+4E00 (the Chinese character for "one" as pronounced by
Japanese).
next prev parent reply other threads:[~2011-07-18 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87myeydbea.fsf@jidanni.org>
[not found] ` <m3d3hifbz8.fsf@quimbies.gnus.org>
2011-07-16 18:21 ` zap-to-char too raw, or document Lars Magne Ingebrigtsen
2011-07-17 0:23 ` Stephen J. Turnbull
2011-07-17 8:01 ` David Kastrup
2011-07-17 9:34 ` Andreas Röhler
2011-07-17 11:18 ` Andreas Schwab
2011-07-17 17:36 ` Andreas Röhler
2011-07-18 13:39 ` Stephen J. Turnbull [this message]
2011-07-20 15:02 ` bug#1580: " Chong Yidong
2011-07-20 20:09 ` Lars Magne Ingebrigtsen
2011-07-21 16:19 ` Chong Yidong
2011-07-21 19:16 ` Glenn Morris
2011-07-31 15:33 ` Lars Magne Ingebrigtsen
2012-04-10 2:24 ` Lars Magne Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hb6jso6w.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).