all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: 17742@debbugs.gnu.org
Subject: bug#17742: Limitations of enchant
Date: Mon, 15 Sep 2014 13:06:55 +0200	[thread overview]
Message-ID: <CAOnWdojtQ5mihHvngsrLs3r5vYSfBvDdjjxA2ij5WDc_=_24Tg@mail.gmail.com> (raw)
In-Reply-To: <CAOnWdogPF5AJ2RU1pFXB2GhAGdR4sx5Kx1gatm_vF=2cEg3cJw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

Since I didn't get any replies, I thought it might be worth noting what I'm
sure some developer must already know, namely that enchant doesn't
currently (v1.6.0) fully support the ispell pipe protocol. In particular,
it doesnt seem to understand either adding words to the dictionary, nor
saving the personal dictionary. In the former case it simply spell-checks
the line, a result which Emacs ignores; in the latter, it gives an empty
reply, and Emacs ignores the fact that it didn't get an "OK" result ("*").

There are still Emacs bugs here: I can't see in the code that Emacs ignores
these failures on purpose, so it should detect and report them. Enchant can
still be used to check spelling on a per-session basis (so maybe it's worth
making the failures warnings rather than errors) but the user shouldn't be
encouraged to believe that it's all working fine.

Obviously, it would be nice if upstream enchant could be made to add this
functionality in the pipe mode: since it's already implemented in
libenchant, that should be easy. Or, as I previously suggested, Emacs could
simply use libenchant and forget about the pipe interface.

-- 
http://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 1379 bytes --]

  reply	other threads:[~2014-09-15 11:06 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 ` Reuben Thomas [this message]
2016-12-02  0:15   ` bug#17742: Limitations of enchant 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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAOnWdojtQ5mihHvngsrLs3r5vYSfBvDdjjxA2ij5WDc_=_24Tg@mail.gmail.com' \
    --to=rrt@sc3d.org \
    --cc=17742@debbugs.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.