all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Björn Lindqvist" <bjourne@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67045@debbugs.gnu.org
Subject: bug#67045: No way to control location of .aspell.en.prepl from within Emacs
Date: Fri, 10 Nov 2023 22:33:17 +0100	[thread overview]
Message-ID: <CALG+76cAhACdf+6eEuR3H1MJZgqYL7A9G98CCf4MubAOzzDKWA@mail.gmail.com> (raw)
In-Reply-To: <83jzqpy2mi.fsf@gnu.org>

I didn't know about that variable and it's not in the manual afaics. I
managed to piece some elisp together using it to set the --repl
option. It works, though I don't think it is a very user-friendly
solution.

Den fre 10 nov. 2023 kl 17:50 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > From: Björn Lindqvist <bjourne@gmail.com>
> > Date: Fri, 10 Nov 2023 17:01:04 +0100
> >
> > During operation aspell creates two files; .aspell.en.pws,
> > .aspell.en.prepl ("en" is of course the language code). By default
> > these files are placed in ~/. You can control the location of
> > .aspell.en.pws by setting the ispell-personal-dictionary variable. But
> > you cannot control the location of .aspell.en.prepl.
> >
> > So a new customization variable is needed to control the location of
> > .aspell.en.prepl. Perhaps named
> > ispell-personal-replacement-dictionary. It should be mapped to
> > aspell's --repl option which controls where the personal replacement
> > dictionary is stored.
>
> Can't you customize ispell-extra-args?  In addition,
> ispell-dictionary-alist supports language-specific options, AFAIK.



-- 
mvh/best regards Björn Lindqvist





  reply	other threads:[~2023-11-10 21:33 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 [this message]
2023-11-11  6:58     ` Eli Zaretskii
2023-11-11 16:39       ` Björn Lindqvist
2023-12-24 20:10       ` Stefan Kangas

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=CALG+76cAhACdf+6eEuR3H1MJZgqYL7A9G98CCf4MubAOzzDKWA@mail.gmail.com \
    --to=bjourne@gmail.com \
    --cc=67045@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 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.