all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: henri-biard@francemel.fr
Cc: 49039@debbugs.gnu.org
Subject: bug#49039: Aspell in Emacs
Date: Tue, 15 Jun 2021 21:12:22 +0300	[thread overview]
Message-ID: <83v96f2e0p.fsf@gnu.org> (raw)
In-Reply-To: <ea-mime-60c8eb89-4c51-100bbb82@www-7.mailo.com> (henri-biard@francemel.fr)

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

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

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

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

> 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),





  reply	other threads:[~2021-06-15 18:12 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 [this message]
2021-06-15 19:20               ` henri-biard
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

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

  git send-email \
    --in-reply-to=83v96f2e0p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=49039@debbugs.gnu.org \
    --cc=henri-biard@francemel.fr \
    /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.