From: O G <opngid@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61190@debbugs.gnu.org
Subject: bug#61190: 28.2; ispell personal dictionary location for hunspell engine
Date: Sat, 11 Feb 2023 12:07:36 -0500 [thread overview]
Message-ID: <CAEc003dwpXavG_5qhNwO828ezGZWJn43q=b69F7C71GxkrYN7w@mail.gmail.com> (raw)
In-Reply-To: <83a61x1sc3.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
On Wed, Feb 1, 2023 at 7:30 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: O G <opngid@gmail.com>
> > Date: Wed, 1 Feb 2023 00:58:56 -0500
> > Cc: 61190@debbugs.gnu.org
> >
> >Please be sure you are testing this correctly. Here's a step by step
> >procedure starting from "emacs -Q":
>
> > emacs -Q
> > M-: (setq ispell-program-name "hunspell") RET
> > M-: (setq ispell-personal-dictionary "C:/Users/xxxx/.hunspell_en_US")
> RET
>
> > Now go to some word in *scratch* and type M-$.
>
> > Then look with Process Explorer how Emacs invoked Hunspell.
>
> >When I do the above, I clearly see the "-p PDICT" command-line
> >arguments with which Emacs invokes Hunspell. I made a point of
> >testing this on Windows with Emacs 28.2, which is what you have, and
> >it worked for me.
>
Thanks for the detailed suggestions -- it now works.
From what I can tell, the issue was the double backslashes not being
accepted
in the file path for the hunspell personal dictionary.
> If the above procedure works for you, please see what you are doing
> differently in your "normal" Emacs sessions. In any case, using
> ispell-cmd-args is not the recommended method; you should instead
> customize the variable ispell-personal-dictionary, which is provided
> for this purpose, and customize it before starting the spell-checker,
> or restart the spell-checker with "M-x ispell-change-dictionary" after
> customizing.
>
[-- Attachment #2: Type: text/html, Size: 2214 bytes --]
next prev parent reply other threads:[~2023-02-11 17:07 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEc003dwpXavG_5qhNwO828ezGZWJn43q=b69F7C71GxkrYN7w@mail.gmail.com' \
--to=opngid@gmail.com \
--cc=61190@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.