unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 18:37:03 +0200	[thread overview]
Message-ID: <831sxlj9ow.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdojiOCm7H4NA=9DJ422u4fcW0JdbrHuKUCx5Bw0D69GqSQ@mail.gmail.com> (message from Reuben Thomas on Tue, 6 Dec 2016 16:20:24 +0000)

> From: Reuben Thomas <rrt@sc3d.org>
> Date: Tue, 6 Dec 2016 16:20:24 +0000
> Cc: 25107@debbugs.gnu.org
> 
>  Why is it useful to remove this information? The documentation of the
>  spell-checkers themselves leaves a lot to be desired, so asking the
>  users to go consult it might not be appreciated. I'd rather add here
>  the missing info about the other spellers.
> 
> ​Emacs is enough for us to document without trying to document third-party software. Since all the software
> involved is free, better to fix it directly, and benefit all its users, rather than take on the burden of documenting
> it in order only to benefit Emacs users.

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.

>  > * lisp/textmodes/ispell.el (ispell-version): Since ispell.el is now
>  > firmly part of Emacs, and the version hasn’t changed since 2003, and
>  > isn’t used anywhere, remove it. 3rd-party code can better use the
>  > Emacs version, or feature or function checks.
> 
>  I agree, but instead of removing the information, how about replacing
>  it with the Emacs version? Something like "ispell.el from Emacs %s".
> 
> The context is an interactive call to ispell-check-version, which reports what version of the spell-checker is
> being used. If the user wishes to know what version of Emacs they are running, they can check
> emacs-version.

I was thinking about someone using the result to report the version
they have, e.g. as part of a bug report.





  reply	other threads:[~2016-12-06 16:37 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 [this message]
2016-12-06 17:46             ` Reuben Thomas
2016-12-06 18:01               ` Eli Zaretskii
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=831sxlj9ow.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).