From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 'Eli Zaretskii' <eliz@gnu.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: RE: bug#10385: e binding in info-mode
Date: Sat, 7 Jan 2012 14:15:45 -0800 [thread overview]
Message-ID: <76BD385B7317495CAE8E5EBFE545A1BB@us.oracle.com> (raw)
In-Reply-To: <878vljchjo.fsf@mail.jurta.org>
> >> There is more trouble when this obsolete feature
> >
> > Since when is it obsolete?
>
> Since its inception. Info-edit was never documented in info.texi.
> (And perhaps references to `Info-edit-map' should be removed
> from elisp.texi)
That a feature is not documented everywhere, or is poor or misguided, does not
mean that it is obsolete.
It is certainly not the case that a command that has been bound to a key
(especially for decades) can be said to be undocumented or invisible/unknown to
users. Let alone considered obsolete.
Think how many commands and key bindings are not documented in any manual. They
are certainly not all - or even any of them - "obsolete" since their inception.
Emacs documentation is not limited to manuals, and user awareness of features is
not even limited to any form of documentation. We provide source code, and that
is the foundation of user communication.
Typically, for a feature or a product to be considered obsolete (officially), it
must first be officially deprecated. And typically there is a period of time
between deprecation and obsolescence - typically a relatively major release or
more.
Typically, an obsolete feature is no longer supported, and a deprecated feature
is still supported.
For example, it might be decided to announce the deprecation of this option in
24.1, and then make it obsolete in 24.2 (since Emacs point releases are
relatively major).
Given such a decision, it would change from a defcustom to a defvar, or even be
eliminated altogether, in 24.2, depending on what was intended wrt desupport (as
an option or even as a variable).
> > Why does it hurt for this to be a defcustom?
>
> Think about a novice looking at the available options
> in the Customization group `info'. It would be a disservice
> to teach them that editing Info nodes is a good idea.
The existence of a user option is not the same thing as suggesting that changing
its value is necessarily a good idea. We have lots of user options that it
might not be a good idea for a novice, in particular, to customize. We provide
plenty of rope for users to hang themselves, often even using only Customize.
next prev parent reply other threads:[~2012-01-07 22:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201112272237.pBRMbo8C022896@freefriends.org>
[not found] ` <62fwftxnbz.fsf@fencepost.gnu.org>
2012-01-06 15:54 ` bug#10385: e binding in info-mode Drew Adams
2012-01-06 16:07 ` Eli Zaretskii
2012-01-07 0:12 ` Richard Stallman
2012-01-07 20:27 ` Juri Linkov
2012-01-07 21:26 ` Drew Adams
2012-01-07 21:46 ` Juri Linkov
2012-01-07 22:15 ` Drew Adams [this message]
2012-01-07 23:10 ` Juri Linkov
2012-01-07 23:27 ` Drew Adams
2012-01-07 23:47 ` Juri Linkov
2012-01-08 1:08 ` Drew Adams
2012-01-08 5:38 ` Richard Stallman
2012-01-08 7:03 ` Drew Adams
2012-01-08 8:21 ` Eli Zaretskii
2012-01-08 22:34 ` Richard Stallman
2012-01-08 23:00 ` Drew Adams
2012-01-09 15:55 ` Richard Stallman
2012-01-08 5:38 ` Richard Stallman
2012-01-08 7:02 ` Drew Adams
2012-01-08 5:37 ` Richard Stallman
2012-01-08 14:13 ` Stefan Monnier
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=76BD385B7317495CAE8E5EBFE545A1BB@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=rms@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 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).