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 14:19:17 -0500 [thread overview]
Message-ID: <CAEc003dSxNyA3ipioyDDqXGqcKymDA2AO1FgY8-MWRNMu6o6pg@mail.gmail.com> (raw)
In-Reply-To: <83sffchx8y.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1574 bytes --]
Okay, the double backslash works with emacs -Q on my system as well.
Back in my customizations, it looks like I had not rechecked by setting the
ispell-personal-dictionary variable ... was still using the ispell-cmd-args
approach unfortunately. So it looks like the latter is the issue, because
everything works now per your suggested settings.
I had originally tried using ispell-personal-dictionary before turning to
ispell-cmd-args and now believe that I may have failed to touch the
.hunspell_en_US file first (a known quirk) while I was testing the double
backslashes among other ways of specifying the file path.
So it's safe to close the bug now.
On Sat, Feb 11, 2023 at 1:29 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: O G <opngid@gmail.com>
> > Date: Sat, 11 Feb 2023 13:16:21 -0500
> > Cc: 61190@debbugs.gnu.org
> >
> > So I guess we can close this bug now?
> >
> > Yes, with the caveat that it would be nice to document this somewhere.
>
> I'll try to find a place to mention this.
>
> > > From what I can tell, the issue was the double backslashes not being
> accepted
> > > in the file path for the hunspell personal dictionary.
> >
> > It should works either way. Maybe you didn't double every backslash?
> >
> > Just double-checked my setup and indeed the problem reappears when I
> substitute
> > double backslashes for all of the forward slashes.
>
> Doesn't happen here. Please show the exact settings you used. Was
> that in "emacs -Q" or with your customizations? If the latter,
> perhaps some of your customizations get in the way.
>
[-- Attachment #2: Type: text/html, Size: 2216 bytes --]
next prev parent reply other threads:[~2023-02-11 19:19 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 [this message]
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
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=CAEc003dSxNyA3ipioyDDqXGqcKymDA2AO1FgY8-MWRNMu6o6pg@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 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).