[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: zap-to-char too raw, or document
From: |
Stephen J. Turnbull |
Subject: |
Re: zap-to-char too raw, or document |
Date: |
Mon, 18 Jul 2011 22:39:19 +0900 |
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).
Re: bug#1580: zap-to-char too raw, or document, Chong Yidong, 2011/07/20