all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Jürgen Hartmann" <juergen_hartmann_@hotmail.com>
Cc: 20870@debbugs.gnu.org
Subject: bug#20870: 24.5; [PATCH] Options presented in ispell *Choices* should be accessible	via keyboard
Date: Sat, 27 Jun 2015 14:47:28 +0300	[thread overview]
Message-ID: <83egkx74q7.fsf@gnu.org> (raw)
In-Reply-To: <DUB124-W5886C85E0A9A0C51F9B9AA8AC0@phx.gbl>

> From: Jürgen Hartmann <juergen_hartmann_@hotmail.com>
> Date: Sat, 27 Jun 2015 12:36:13 +0200
> 
> The attached patch tries to offer a workaround for this bug and to provide a
> feature that was asked for by Emanuel Berg in
> 
>    http://lists.gnu.org/archive/html/help-gnu-emacs/2015-06/msg00363.html
> 
> i.e. that Ispell uses certain keys in a certain order for the offers in its
> *Choices* buffer.
> 
> 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.





  reply	other threads:[~2015-06-27 11:47 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 [this message]
2015-06-28  5:02     ` Stefan Monnier
2020-08-25  9:07     ` Lars 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83egkx74q7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20870@debbugs.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.