From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Jürgen Hartmann" <juergen_hartmann_@hotmail.com>, 20870@debbugs.gnu.org
Subject: bug#20870: 24.5; [PATCH] Options presented in ispell *Choices* should be accessible via keyboard
Date: Tue, 25 Aug 2020 11:07:29 +0200 [thread overview]
Message-ID: <87blizdrfy.fsf@gnus.org> (raw)
In-Reply-To: <83egkx74q7.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 27 Jun 2015 14:47:28 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Therefore, the idea is to use a customizable variable to hold a vector of key
>> specifications that are used by ispell-command-loop in the given order to
>> assemble its options.
>
> Thanks, but isn't it better to simply use numbers longer than one
> digit? E.g., if the number of choices is more than 10, use 00, 01,
> etc.; if the number of choices is more than 100, use 000, 001,
> etc., and so on and so forth? Bonus points for being able to support
> responses like 1 and 10 when the number of choices is more than 100
> (but this is a nicety, not really required IMO).
>
> I just cannot imagine anyone in the need for customizing this.
I think that would be a better interface, too, so the patch isn't ideal,
and I'm closing this bug report. If somebody wants to work on Eli's
suggestion, a new bug report would perhaps be appropriate.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2020-08-25 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 9:08 bug#20870: 24.5; Options presented in ispell *Choices* should be accessible via keyboard Jürgen Hartmann
2015-06-27 10:36 ` bug#20870: 24.5; [PATCH] " Jürgen Hartmann
2015-06-27 11:47 ` Eli Zaretskii
2015-06-28 5:02 ` Stefan Monnier
2020-08-25 9:07 ` Lars Ingebrigtsen [this message]
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=87blizdrfy.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=20870@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juergen_hartmann_@hotmail.com \
/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.