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: 49039@debbugs.gnu.org
Subject: bug#49039: Aspell in Emacs
Date: Tue, 15 Jun 2021 21:20:29 +0200 (CEST)	[thread overview]
Message-ID: <ea-mime-60c8fd7d-7e3-3ecf65b4@www-7.mailo.com> (raw)
In-Reply-To: <83v96f2e0p.fsf@gnu.org>

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

From: Eli Zaretskii <eliz@gnu.org>
To: henri-biard@francemel.fr
Subject: Re: bug#49039: Aspell in Emacs
Date: 15/06/2021 20:12:22 Europe/Paris
Cc: 49039@debbugs.gnu.org

>> From: henri-biard@francemel.fr
>> Cc: 49039@debbugs.gnu.org
>> Date: Tue, 15 Jun 2021 20:03:53 +0200 (CEST)
>> 
>> > > It looks to me that it is basically a hack of ispell, likely the result that it was easier 
>> > > and quicker for the developer to do it that way. Correct me if I am wrong.
>> 
>> > You are wrong. Please read the code, don't just judge it by the name
>> of the package (which is just a historic incident).
>> 
>> It is valuable to go past the historic after significant time has passed as it easily leads
>> to confusion or obfuscation.
>> 
>> May I suggest that the generic framework uses a name which in different that using
>> the old ispell name. And within that framowork, one could call ispell, aspell or whatever,
>> so there is no longer a conflict of understanding between ispell the framework and ispell
>> the program.

>We are not going to change the names, sorry. Too many Emacs users are
>used to these names.



Then it would be good to have the program ispell deprecated and letting aspell

take over, following the Gnu Project Plan.



>> > > Had tried lookinf for the self documentation for ispell-program-name, but could not 
>> > > access anything.
>> 
>> > "C-h v ispell-program-name RET" would have shown its documentation.
>> 
>> There are no matches for ispell-program-name if you try to do C-h v ispell-program-name

>There will be once you invoke the first ispell-* command.



Let's try to avoid such requirement and have the ability to access that information

without having to call other ispell commands first.  There could be ispell-mode, once

a user activates it, the documentation for all ispell functionality would be available.



>> > In any case, since Emacs already looks for known spell-checkers, and
>> > already prefers aspell, my conclusion from the fact that it didn't
>> > work for you is that you have some unusual setup, which should be
>> > quite rare nowadays. The defaults are set such that the user will not
>> > need to know about this variable.
>> 
>> There has been a misunderstanding that aspell was not working. It was 
>> working but my impression was that using ispell on emacs was using
>> ispell the program.
>> 
>> I am convinced that the user should know about the variable. It is an important
>> variable and users should know what spell checker is being used.

>Then I'm sorry, but we will have to agree to disagree on that.



Or be able to get to know about it from emacs self documentation and from manual.

I frequently try to get information from emacs.  Emacs has too many hidden things.



The added benefit would be that people would know about the standalone program.

Or do people not really use spell checker in emacs much?



>> > IOW, spelling with aspell in Emacs should work as long as invoking
>> > aspell from the shell prompt works. If it doesn't work to invoke
>> > aspell from the shell prompt, then you should first correct your
>> > system's configuration so that it does.
>> 
>> Correct, but it is hard to understand what spelling program is being used.

>You can always ask. Like here: you asked and got the answer.



Yes, but do you really wanted users to always have to ask.  And do users really

want to have to ask to know.  Personally, I want to get on with my work, without

wasting time asking about this and that.  Would also avoid the frustration of people

responding to tho same question over and over again.  From operational point of

view, when a question is being asked too frequently, it is indication of some deficit.



>> Gnu packages should work well together. The Gnu Aspell manual says that 
>> Aspell is a Free and Open Source spell checker designed to eventually replace
>> Ispell.This creates confusion and emacs should stop using ispell by name,
>> except when it is actually using the ispell checker.

>You are again sticking to the name. The name is not important: I'm

>quite sure Emacs was using aspell on your system (if it is installed),



Good. I wanted to use aspell.  Am not sticking with the name, but it is time for gnu

to deprecate the ispell program in favour of aspell.  It would then be much easier for

emacs users to to consider ispell in emacs as the general framework for orthographic

correction.







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

  reply	other threads:[~2021-06-15 19:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-15 13:41 bug#49039: Aspell in Emacs henri-biard
2021-06-15 14:24 ` Eli Zaretskii
2021-06-15 15:05   ` Lars Ingebrigtsen
2021-06-15 15:09   ` henri-biard
2021-06-15 15:26     ` Eli Zaretskii
2021-06-15 17:00       ` henri-biard
2021-06-15 17:30         ` Eli Zaretskii
2021-06-15 17:51           ` Eli Zaretskii
2021-06-15 18:09             ` henri-biard
2021-06-15 18:03           ` henri-biard
2021-06-15 18:12             ` Eli Zaretskii
2021-06-15 19:20               ` henri-biard [this message]
2021-06-15 19:25               ` 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-60c8fd7d-7e3-3ecf65b4@www-7.mailo.com \
    --to=henri-biard@francemel.fr \
    --cc=49039@debbugs.gnu.org \
    --cc=eliz@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).