unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 61190@debbugs.gnu.org, opngid@gmail.com
Subject: bug#61190: 28.2; ispell personal dictionary location for hunspell engine
Date: Wed, 01 Feb 2023 20:31:23 +0200	[thread overview]
Message-ID: <83edr9z18k.fsf@gnu.org> (raw)
In-Reply-To: <86h6w5eose.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 01 Feb 2023 19:58:17 +0200)

> From: Juri Linkov <juri@linkov.net>
> Cc: opngid@gmail.com,  61190@debbugs.gnu.org
> Date: Wed, 01 Feb 2023 19:58:17 +0200
> 
> > I looked into the Hunspell's sources, and I think I know why this
> > happens.  Hunspell has a peculiar logic when looking for the personal
> > dictionary.  The outcome of that peculiar logic is that if Hunspell is
> > invoked with "-p PDICT" command-line argument, and PDICT is an
> > absolute file name, that file must already exist, or else Hunspell
> > will decide it cannot use it.  And Emacs always invokes Hunspell with
> > an absolute file name of the personal dictionary.
> >
> > This is arguably a bug in Hunspell, but a workaround is to create an
> > empty file at the location where you want the personal dictionary to
> > be, and then restart the speller.
> 
> This bug exists even on GNU/Linux, so requires such customization:
> 
>   (unless (file-exists-p "~/.hunspell")
>     (shell-command "touch ~/.hunspell"))
>   (setq ispell-personal-dictionary "~/.hunspell")

Yes, the code which does that in Hunspell is not Windows-specific.





  reply	other threads:[~2023-02-01 18:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-31  0:53 bug#61190: 28.2; ispell personal dictionary location for hunspell engine O G
2023-01-31 13:47 ` Eli Zaretskii
2023-01-31 15:02   ` Eli Zaretskii
     [not found]     ` <CAEc003eWkHFf2Ta1vJfEFQjXJPS9=xB0doRUP+HedcbuNuPPSQ@mail.gmail.com>
2023-02-01  3:35       ` Eli Zaretskii
2023-02-01  5:58         ` O G
2023-02-01 12:30           ` Eli Zaretskii
2023-02-11 17:07             ` O G
2023-02-11 17:14               ` Eli Zaretskii
2023-02-11 18:16                 ` O G
2023-02-11 18:29                   ` Eli Zaretskii
2023-02-11 19:19                     ` O G
2023-02-12 12:07                       ` Eli Zaretskii
2023-02-12 12:07                     ` Eli Zaretskii
2023-02-01 17:58     ` Juri Linkov
2023-02-01 18:31       ` Eli Zaretskii [this message]
2023-07-02 19:19 ` bug#61190: follow-up on ispell-personal-dictionary issue for hunspell O G

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=83edr9z18k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61190@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=opngid@gmail.com \
    /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).