From: Daimrod <daimrod@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18023@debbugs.gnu.org
Subject: bug#18023: 24.3.92; [PATH] Missing fallback in latin-postfix input method
Date: Tue, 22 Jul 2014 13:38:29 +0900 [thread overview]
Message-ID: <874mya80u2.fsf@tanger.home> (raw)
In-Reply-To: <83a9823vhr.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 22 Jul 2014 06:47:28 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Daimrod <daimrod@gmail.com>
>> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 18023@debbugs.gnu.org
>> Date: Tue, 22 Jul 2014 09:28:26 +0900
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> >> Date: Mon, 21 Jul 2014 14:33:44 -0400
>> >> Cc: 18023@debbugs.gnu.org
>> >>
>> >> > This patch permits the user to type " _" using the latin-postfix input
>> >> > method. ATM the user has to use the following sequence:
>> >> > `SPC SPC DEL _'
>> >>
>> >> I have no objection to the patch, but don't have time to evaluate it
>> >> (I'm travelling and only have occasionally Internet access).
>> >
>> > FWIW, it strikes me that "C-q _" is less typing.
>>
>> It's not consistent and it doesn't really save typing:
>> - "SPC _ _"
>> - "SPC C-q _"
>
> I meant "SPC SPC DEL _". As for "SPC _ _", it's of the same length,
> so it doesn't save typing, either.
It wasn't clear in my initial message so it's my fault. In my patch, I
update the latin-postfix input-method so that one can type "SPC _ _"
instead of "SPC SPC DEL _".
Though I agree that it doesn't save typing compared to the method you
proposed, my approach saves typing compared to the current method and I
find my method faster to type because it's consistent with the other
combinations and it doesn't "break the flow".
--
Daimrod/Greg
next prev parent reply other threads:[~2014-07-22 4:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 7:57 bug#18023: 24.3.92; [PATH] Missing fallback in latin-postfix input method Daimrod
2014-07-21 15:06 ` Daimrod
2014-07-21 18:33 ` Stefan Monnier
2014-07-21 18:38 ` Eli Zaretskii
2014-07-22 0:28 ` Daimrod
2014-07-22 3:47 ` Eli Zaretskii
2014-07-22 4:38 ` Daimrod [this message]
2014-07-25 8:12 ` Eli Zaretskii
2014-07-26 2:26 ` Daimrod
2014-08-04 17:45 ` Daimrod
2014-08-11 0:44 ` Glenn Morris
2014-08-11 12:20 ` Daimrod
2014-07-24 14:09 ` K. Handa
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=874mya80u2.fsf@tanger.home \
--to=daimrod@gmail.com \
--cc=18023@debbugs.gnu.org \
--cc=eliz@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).