From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 17742@debbugs.gnu.org
Subject: bug#17742: Acknowledgement (Support for enchant?)
Date: Wed, 14 Dec 2016 17:42:04 +0200 [thread overview]
Message-ID: <83twa6a56b.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdojx6SXSQTd73a64mPuRWWOps=xN4uVtc4ZxbRA6BDMa9Q@mail.gmail.com> (message from Reuben Thomas on Tue, 13 Dec 2016 21:17:25 +0000)
> From: Reuben Thomas <rrt@sc3d.org>
> Date: Tue, 13 Dec 2016 21:17:25 +0000
> Cc: 17742@debbugs.gnu.org
>
> I'm okay with installing this, provided that the above-mentioned issue
> is taken care of, if only by leaving it to the user to provide the
> dictionary entries by hand. I don't think it's a good idea to
> auto-generate entries that are only 80% correct, as that will
> certainly trigger bug reports.
>
> Agreed. I have prepared a separate patch (so it can be easily reverted later) to disable the use of
> ispell-find-enchant-dictionaries, along with a rationale in comments.
>
> If that is satisfactory, I can add NEWS documentation for the new feature, along with a warning about its
> limitations, and install the patches.
OK, I guess. Maybe add in a comment an example of setting up Enchant
for some language, in case users may find that helpful.
Thanks.
next prev parent reply other threads:[~2016-12-14 15:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 0:01 bug#17742: Support for enchant? Reuben Thomas
2014-09-15 11:06 ` bug#17742: Limitations of enchant Reuben Thomas
2016-12-02 0:15 ` Reuben Thomas
[not found] ` <handler.17742.B.140235850213377.ack@debbugs.gnu.org>
2016-12-05 21:41 ` bug#17742: Acknowledgement (Support for enchant?) Reuben Thomas
2016-12-06 15:55 ` Eli Zaretskii
2016-12-06 15:56 ` Reuben Thomas
2016-12-13 0:53 ` Reuben Thomas
2016-12-13 16:37 ` Eli Zaretskii
2016-12-13 18:26 ` Reuben Thomas
2016-12-13 18:54 ` Eli Zaretskii
2016-12-13 21:17 ` Reuben Thomas
2016-12-13 21:30 ` Reuben Thomas
2016-12-14 15:42 ` Eli Zaretskii [this message]
2016-12-15 12:36 ` Reuben Thomas
2016-12-18 23:39 ` Reuben Thomas
2016-12-19 1:02 ` Reuben Thomas
2016-12-19 12:41 ` Reuben Thomas
2016-12-19 16:01 ` Eli Zaretskii
2016-12-19 17:37 ` Agustin Martin
2016-12-19 18:09 ` Eli Zaretskii
2016-12-19 21:21 ` Reuben Thomas
2016-12-19 21:27 ` Reuben Thomas
2016-12-20 15:38 ` Eli Zaretskii
2016-12-19 21:47 ` Reuben Thomas
2016-12-19 22:04 ` Reuben Thomas
2016-12-20 15:40 ` Eli Zaretskii
2016-12-20 15:40 ` Eli Zaretskii
2016-12-20 21:43 ` Reuben Thomas
2016-12-21 17:13 ` Eli Zaretskii
2016-12-21 17:32 ` Reuben Thomas
2017-08-09 11:35 ` Reuben Thomas
2017-08-18 8:54 ` Eli Zaretskii
2017-08-20 13:02 ` Reuben Thomas
2017-08-20 14:42 ` Eli Zaretskii
2017-08-20 14:50 ` Reuben Thomas
2017-08-20 19:34 ` Eli Zaretskii
2017-08-20 20:36 ` Reuben Thomas
2017-08-20 14:50 ` bug#17742: Reuben Thomas
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=83twa6a56b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17742@debbugs.gnu.org \
--cc=rrt@sc3d.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).