From: Reuben Thomas <rrt@sc3d.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25107@debbugs.gnu.org
Subject: bug#25107: Acknowledgement (Patches to clean up ispell.el)
Date: Tue, 6 Dec 2016 18:11:16 +0000 [thread overview]
Message-ID: <CAOnWdohh4erePR5xzvef3rwUjK9qJ-dTYXMnFMGoeWeSvTfLiA@mail.gmail.com> (raw)
In-Reply-To: <83y3zthr75.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2252 bytes --]
On 6 December 2016 at 18:01, Eli Zaretskii <eliz@gnu.org> wrote:
> > 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.
>
My understanding is that it exists for reporting bugs in the combination
of ispell.el and whatever spell checker you are using. When ispell.el was
distributed as third-party code, there were extra two useful pieces of
information: the version of the spell-checker program, and the version of
ispell.el.
Now, there is just one extra piece of information, the version of the
spell-checker program.
One would presumably also want the version of Emacs in a bug report, but we
don't print this out all over the place; we provide the convenience of
report-emacs-bug, and otherwise expect users to put it manually in the
report.
So, emacs-version does not substitute for the old ispell.el version; the
old ispell.el version has simply become unnecessary, and I've removed it.
The Emacs version is still needed for a bug report, but there's no reason
that ispell.el (or any other core package) should show emacs-version
specially, when there are already user-friendly ways to automatically put
it in bug reports.
--
http://rrt.sc3d.org
[-- Attachment #2: Type: text/html, Size: 3325 bytes --]
next prev parent reply other threads:[~2016-12-06 18:11 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
2016-12-06 18:11 ` Reuben Thomas [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOnWdohh4erePR5xzvef3rwUjK9qJ-dTYXMnFMGoeWeSvTfLiA@mail.gmail.com \
--to=rrt@sc3d.org \
--cc=25107@debbugs.gnu.org \
--cc=eliz@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.