unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 20:24:27 +0200 (CEST)	[thread overview]
Message-ID: <ea-mime-60c8f05b-5b74-6588b651@www-7.mailo.com> (raw)
In-Reply-To: <831r933udd.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1992 bytes --]

>From: Eli Zaretskii <eliz@gnu.org>
>To: henri-biard@francemel.fr
>Subject: Re: bug#49037: flyspell word correction frustrating
>Date: 15/06/2021 19:33:50 Europe/Paris
>Cc: larsi@gnus.org;
>   49037@debbugs.gnu.org

>> From: henri-biard@francemel.fr
>> Cc: larsi@gnus.org,
>> 49037@debbugs.gnu.org
>> Date: Tue, 15 Jun 2021 19:08:48 +0200 (CEST)
>> 
>> >> If it was good information I would not complain.
>> 
>> >What is not good about it?
>> 
>> For instance:
>> 
>> 1. It does not tell me that aspell is the default

>Why should it? You set up your system with whatever spell-checker you
>want, and Emacs uses that. It is not Emacs's business to tell you
>which spell-checker to install and use.



I have multiple ones and make comparisons between them.  So I really want to know

what it uses.  After all the information is there and that is what emacs actually does.

Should I not be able to easily know what it is doing under the hood.  Emacs Self

Documentation should help me with that.



>> 2. It does not tell me that even when I use ispell-word, it might actually
>> do something else (aspell-word maybe).

>ispell-word is a command, it is unrelated to the program being
>invoked. The manual clearly says that those commands can work with
>any one of the 4 supported spell-checkers.

>> 3. It does not describe that it searches PATH.

>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.



Because Gnu Aspell was designed to replace Ispell, how about deprecating Ispell

and simply have emacs-ispell be the general framework for orthographic study.



That would certainly solve the problem.



Would appreciate if you do not consider me a "Bad Actor".  





[-- Attachment #2: Type: text/html, Size: 2447 bytes --]

  reply	other threads:[~2021-06-15 18:24 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 [this message]
2021-06-15 18:29                 ` Eli Zaretskii
2021-06-15 19:35                   ` henri-biard
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-60c8f05b-5b74-6588b651@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).