From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 25107@debbugs.gnu.org
Subject: bug#25107: Acknowledgement (Patches to clean up ispell.el)
Date: Tue, 06 Dec 2016 20:01:50 +0200 [thread overview]
Message-ID: <83y3zthr75.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdoi7Nnw9PE0bkPeaNT8mB-wpwa_x9nErJ+mbqfdC576gTg@mail.gmail.com> (message from Reuben Thomas on Tue, 6 Dec 2016 17:46:23 +0000)
> From: Reuben Thomas <rrt@sc3d.org>
> Date: Tue, 6 Dec 2016 17:46:23 +0000
> Cc: 25107@debbugs.gnu.org
>
> I agree with the general point, but in this case we are talking about
> mentioning a small number of file names in the doc string. Doesn't
> seem like a burden to me, and whoever put that information there
> probably didn't see it as such, either.
>
> In that case I will add the information for Enchant. At least it is not likely to change.
Sure, that's what I meant.
> I was thinking about someone using the result to report the version
> they have, e.g. as part of a bug report.
>
> Version of what? If of Emacs, then that version information is already provided by report-emacs-bug. If of a
> spellchecker, then that information is still provided by the revised message.
It's admittedly a minor issue, but just to make myself clear: I
thought about reporting the version not as part of report-emacs-bug.
Or let me ask this: why does ispell-version at all exist? Perhaps I'm
confused about its purpose.
next prev parent reply other threads:[~2016-12-06 18:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 17:10 bug#25107: Patches to clean up ispell.el Reuben Thomas
[not found] ` <handler.25107.B.148087148014808.ack@debbugs.gnu.org>
2016-12-04 22:11 ` bug#25107: Acknowledgement (Patches to clean up ispell.el) Reuben Thomas
2016-12-05 21:38 ` Reuben Thomas
2016-12-06 15:51 ` Eli Zaretskii
2016-12-06 16:20 ` Reuben Thomas
2016-12-06 16:37 ` Eli Zaretskii
2016-12-06 17:46 ` Reuben Thomas
2016-12-06 18:01 ` Eli Zaretskii [this message]
2016-12-06 18:11 ` Reuben Thomas
2016-12-06 18:41 ` Eli Zaretskii
2016-12-06 21:58 ` Reuben Thomas
2016-12-13 0:55 ` Reuben Thomas
2016-12-13 16:29 ` Eli Zaretskii
2016-12-13 19:07 ` Reuben Thomas
2016-12-13 19:29 ` Eli Zaretskii
2016-12-13 19:45 ` Reuben Thomas
2016-12-13 19:45 ` bug#25107: 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=83y3zthr75.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25107@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).