From: henri-biard@francemel.fr
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: larsi@gnus.org, 49037@debbugs.gnu.org
Subject: bug#49037: flyspell word correction frustrating
Date: Tue, 15 Jun 2021 21:35:07 +0200 (CEST) [thread overview]
Message-ID: <ea-mime-60c900eb-12e0-250d112f@www-7.mailo.com> (raw)
In-Reply-To: <83sg1j2d8d.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
>> >That's an implementation detail. If you want to know those details,
>> >you have the source to read and study. The user manual explains how
>> >to use the commands, not how the commands work.
>>
>> Explains with no examples or much description of ispell-program-name, which
>> for me is very important.
>Yours is a rare situation, so you shouldn't expect it to be covered in
>the general documentation.
Then I suggest maintainers stop making accusations on users simply because their use
case is a rare occurrence. One cannot expect politeness once you denigrate others
about what is impartant to them or what they are trying to do.
It occurs to me that you do understand, and would be a big improvement if others
follow your example.
Many Gratitudes Eli.
[-- Attachment #2: Type: text/html, Size: 1031 bytes --]
next prev parent reply other threads:[~2021-06-15 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 5:47 bug#49037: flyspell word correction frustrating henri-biard
2021-06-15 15:10 ` Lars Ingebrigtsen
2021-06-15 15:23 ` henri-biard
2021-06-15 15:48 ` Lars Ingebrigtsen
2021-06-15 16:34 ` henri-biard
2021-06-15 16:54 ` Eli Zaretskii
2021-06-15 17:08 ` henri-biard
2021-06-15 17:33 ` Eli Zaretskii
2021-06-15 18:24 ` henri-biard
2021-06-15 18:29 ` Eli Zaretskii
2021-06-15 19:35 ` henri-biard [this message]
2021-06-15 20:00 ` henri-biard
2021-06-15 17:59 ` Glenn Morris
2021-06-15 15:55 ` Robert Pluim
2021-06-15 16:48 ` henri-biard
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=ea-mime-60c900eb-12e0-250d112f@www-7.mailo.com \
--to=henri-biard@francemel.fr \
--cc=49037@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).