unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: opngid@gmail.com
Cc: 61190@debbugs.gnu.org
Subject: bug#61190: 28.2; ispell personal dictionary location for hunspell engine
Date: Sun, 12 Feb 2023 14:07:03 +0200	[thread overview]
Message-ID: <83zg9jgk9k.fsf@gnu.org> (raw)
In-Reply-To: <83sffchx8y.fsf@gnu.org> (message from Eli Zaretskii on Sat, 11 Feb 2023 20:29:01 +0200)

> Cc: 61190@debbugs.gnu.org
> Date: Sat, 11 Feb 2023 20:29:01 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > 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.

Now done.





  parent reply	other threads:[~2023-02-12 12: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
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 [this message]
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=83zg9jgk9k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61190@debbugs.gnu.org \
    --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).