unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>, "Björn Lindqvist" <bjourne@gmail.com>
Cc: 67045@debbugs.gnu.org
Subject: bug#67045: No way to control location of .aspell.en.prepl from within Emacs
Date: Sun, 24 Dec 2023 12:10:54 -0800	[thread overview]
Message-ID: <CADwFkmmvghT-Hey-UwMQ=Bxam6erZXreYNfg2m5s3D2o0E2AmQ@mail.gmail.com> (raw)
In-Reply-To: <837cmoydx2.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> Why do you consider it not a user-friendly solution?  There's no limit
> to command-line options a speller can have, so it is not reasonable
> IMO to expect Emacs to have a separate variable for each one of them.
> Thus, our solution to have a single variable that can hold any
> additional options is a reasonable compromise.
[...]
> Stefan, WDYT?

I could go either way with this one, to be really honest.  Eli is right
that proliferating our user options with all the details of concrete
spell checkers will start getting unwieldy at some point.

Personally, I'd rather see the interface of ispell.el get more
abstracted away from concrete spell checkers.  I don't think users of
Emacs shouldn't have to mess with aspell/ispell/hunspell/enchant (unless
they want to, of course).

So I'm not entirely sure that adding a new user option like this is
moving things in the right thing direction.





      parent reply	other threads:[~2023-12-24 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 16:01 bug#67045: No way to control location of .aspell.en.prepl from within Emacs Björn Lindqvist
2023-11-10 16:49 ` Eli Zaretskii
2023-11-10 21:33   ` Björn Lindqvist
2023-11-11  6:58     ` Eli Zaretskii
2023-11-11 16:39       ` Björn Lindqvist
2023-12-24 20:10       ` Stefan Kangas [this message]

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='CADwFkmmvghT-Hey-UwMQ=Bxam6erZXreYNfg2m5s3D2o0E2AmQ@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=67045@debbugs.gnu.org \
    --cc=bjourne@gmail.com \
    --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).