|
From: | Andreas Röhler |
Subject: | Re: zap-to-char too raw, or document |
Date: | Sun, 17 Jul 2011 11:34:20 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.18) Gecko/20110616 SUSE/3.1.11 Thunderbird/3.1.11 |
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 ñ.
Where is the problem? User specifying a simple char will not notice the extended capability.
For zap-to-char, things look different. So I am with Lars in that there should be different interactive specs
it was said "but allows", not "make different". Better keeping things simple. Andreas for with and without input
methods, like we have s (without input method) and M (with current input method).
[Prev in Thread] | Current Thread | [Next in Thread] |