From: Juri Linkov <juri@jurta.org>
To: rms@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>, drew.adams@oracle.com, emacs-devel@gnu.org
Subject: Re: bug#10385: e binding in info-mode
Date: Sat, 07 Jan 2012 22:27:34 +0200 [thread overview]
Message-ID: <871urckv7k.fsf@mail.jurta.org> (raw)
In-Reply-To: <E1RjJtx-0001XS-VV@fencepost.gnu.org> (Richard Stallman's message of "Fri, 06 Jan 2012 19:12:49 -0500")
> I thought that e would be a useful command
> back when I supposed info files would be written by hand.
> But we don't do that, so e is not useful and maybe only causes trouble.
There is more trouble when this obsolete feature is announced
in the customization group `info' via its customizable variable
`Info-enable-edit'. It would be better to hide it from the
Customization interface by changing `defcustom' to `defvar':
=== modified file 'lisp/info.el'
--- lisp/info.el 2011-12-05 09:52:02 +0000
+++ lisp/info.el 2012-01-07 20:27:15 +0000
@@ -61,14 +61,12 @@
:group 'info
:version "24.1")
-(defcustom Info-enable-edit nil
- "Non-nil means the \\<Info-mode-map>\\[Info-edit] command in Info can edit the current node.
+(defvar Info-enable-edit nil
+ "Non-nil means the `Info-edit' command in Info can edit the current node.
This is convenient if you want to write Info files by hand.
However, we recommend that you not do this.
It is better to write a Texinfo file and generate the Info file from that,
-because that gives you a printed manual as well."
- :type 'boolean
- :group 'info)
+because that gives you a printed manual as well.")
(defvar Info-enable-active-nodes nil
"Non-nil allows Info to execute Lisp code associated with nodes.
next prev parent reply other threads:[~2012-01-07 20:27 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 [this message]
2012-01-07 21:26 ` Drew Adams
2012-01-07 21:46 ` Juri Linkov
2012-01-07 22:15 ` Drew Adams
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=871urckv7k.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).