From: "André A. Gomes" <andremegafone@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: ispell.el and pipes
Date: Tue, 16 Nov 2021 23:40:45 +0300 [thread overview]
Message-ID: <87y25nq1f6.fsf@gmail.com> (raw)
In-Reply-To: <83y25nzx9q.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 16 Nov 2021 22:00:17 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: André A. Gomes <andremegafone@gmail.com>
>> Cc: emacs-devel@gnu.org
>> Date: Tue, 16 Nov 2021 22:40:19 +0300
>>
>> If the old farts (no offence) insist on using *Choices*, then using
>> ascii characters is silly. There should be a variable that gives an
>> upper-bound for spelling suggestions perhaps. If that bound would be 10
>> by default, then just use the digits. Otherwise, the characters used
>> should be latin lower-case english letters. (Typing digits is hard).
>> Either one or two letters, depending on the number of suggestions. That
>> gives as much as (expt 26 2) choices, which is more than enough.
>
> A tempest in a teapot, if you ask me. I'm a heavy user of
> spell-checking, always have been. IME, the correct choice is almost
> always '0', rarely '1', i.e. the very first candidates. If you see
> something else, switch to a different speller. Or use the drop-down
> menu of Flyspell ("C-c $").
What speller do you use, if I may ask?
Well, it's a tempest in a teapot, since you ignored my starting point.
There's a bug, afaik, and I've described it. Let me remind you below.
> Is it even possible to select, i.e. type, a characters that is above
> ?~???
> (The historical reason why Ispell uses digits is that this is how the
> UI of the original Ispell worked; Hunspell still behaves the same even
> today.)
Same for aspell. I'm well aware of these historical details.
On another subject, I wonder what would be worth to burn cycles on. And
how to deal with the idiosyncrasies of the gatekeepers of this
community.
--
André A. Gomes
"Free Thought, Free World"
next prev parent reply other threads:[~2021-11-16 20:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 14:42 ispell.el and pipes André A. Gomes
2021-11-16 15:22 ` Eli Zaretskii
2021-11-16 16:25 ` André A. Gomes
2021-11-16 19:40 ` André A. Gomes
2021-11-16 20:00 ` Eli Zaretskii
2021-11-16 20:40 ` André A. Gomes [this message]
2021-11-17 9:33 ` Robert Pluim
2021-11-17 10:57 ` tomas
2021-11-17 11:01 ` André A. Gomes
2021-11-17 11:08 ` Robert Pluim
2021-11-17 11:16 ` André A. Gomes
2021-11-17 11:27 ` tomas
2021-11-17 12:08 ` dick
2021-11-17 12:48 ` tomas
2021-11-17 12:48 ` Eli Zaretskii
2021-11-17 13:23 ` André A. Gomes
2021-11-17 14:18 ` Eli Zaretskii
2021-11-17 20:19 ` André A. Gomes
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=87y25nq1f6.fsf@gmail.com \
--to=andremegafone@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).