From: Alan Third <alan@idiocy.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 19229@debbugs.gnu.org
Subject: bug#19229: ispell on Windows
Date: Mon, 7 Sep 2020 23:08:37 +0100 [thread overview]
Message-ID: <20200907220837.GD93185@breton.holly.idiocy.org> (raw)
In-Reply-To: <87wo156ylb.fsf@gnus.org>
On Mon, Sep 07, 2020 at 11:55:44PM +0200, Lars Ingebrigtsen wrote:
> Alan Third <alan@idiocy.org> writes:
>
> > I feel that the way ispell handles a misconfigured hunspell is, at the
> > moment, not very helpful. I can provide a patch that I believe makes
> > it fail more gracefully, but I'm getting the feeling it's behaviour
> > that's not wanted.
> >
> > Shall we call it quits?
>
> Reading this thread, it seems like hunspell doesn't work out of the box
> on some systems in Emacs. If Alan has a fix that improves the
> user experience here, that would surely be useful?
Oh, this was so long ago I've no idea what my fix was any more. I'd
assumed this bug report had been closed.
--
Alan Third
next prev parent reply other threads:[~2020-09-07 22:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-30 18:25 bug#19229: ispell-phaf: No matching entry for Alexander Shukaev
2014-11-30 19:50 ` bug#19229: A workaround for hunspell Chris Zheng
2014-12-01 16:26 ` Eli Zaretskii
2014-11-30 21:15 ` bug#19229: ispell-phaf: No matching entry for Eli Zaretskii
2014-11-30 21:55 ` Alexander Shukaev
2014-12-01 16:24 ` Eli Zaretskii
2014-12-01 17:15 ` Alexander Shukaev
2015-05-20 18:53 ` bug#19229: ispell on Windows Alan Third
2015-05-20 19:21 ` Eli Zaretskii
2015-05-20 20:34 ` Alan Third
2015-05-21 2:41 ` Eli Zaretskii
2015-05-21 8:16 ` Alan Third
2015-05-21 16:23 ` Eli Zaretskii
2015-05-21 20:19 ` Alan Third
2015-05-22 6:53 ` Eli Zaretskii
2015-05-22 18:57 ` Alan Third
2015-05-22 19:22 ` Eli Zaretskii
2015-05-22 19:55 ` Alan Third
2015-05-22 20:08 ` Eli Zaretskii
2015-05-22 21:46 ` Jan D.
2020-09-07 21:55 ` Lars Ingebrigtsen
2020-09-07 22:08 ` Alan Third [this message]
2020-09-08 10:12 ` Lars Ingebrigtsen
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=20200907220837.GD93185@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=19229@debbugs.gnu.org \
--cc=larsi@gnus.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).