From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Changes to ELisp manual in revision 106667
Date: Tue, 13 Dec 2011 09:28:53 -0500 [thread overview]
Message-ID: <E1RaTLh-0005Mt-Iu@fencepost.gnu.org> (raw)
In-Reply-To: <87k4601sjh.fsf@gnu.org> (message from Chong Yidong on Tue, 13 Dec 2011 21:59:30 +0800)
> From: Chong Yidong <cyd@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Tue, 13 Dec 2011 21:59:30 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Can you please explain the reason for these changes in the top-level
> > menu? They look gratuitous to me, but maybe I'm missing something.
> >
> > -* Libraries: Lisp Libraries. Creating Lisp programs to run in Emacs.
> > -* Eval: Lisp Eval. Executing a single Lisp expression in Emacs.
> > -* Interaction: Lisp Interaction. Executing Lisp in an Emacs buffer.
> > +* Lisp Libraries:: How Lisp programs are loaded into Emacs.
> > +* Lisp Eval:: Executing a single Lisp expression in Emacs.
> > +* Lisp Interaction:: Executing Lisp in an Emacs buffer.
>
> It seemed not quite right to use the short form, since the rest of the
> items in the menu dealt with stuff like compilation and didn't share a
> common "Lisp" topic prefix. But it's no big deal.
It's a convenience feature: the user types "m Eval RET" instead of "m
Lisp Eval RET". This leaves the node names sufficiently non-generic
to prevent collision, and yet does not punish users by causing them to
type more text.
next prev parent reply other threads:[~2011-12-13 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 12:24 Changes to ELisp manual in revision 106667 Eli Zaretskii
2011-12-13 13:59 ` Chong Yidong
2011-12-13 14:28 ` Eli Zaretskii [this message]
2011-12-15 21:39 ` Juri Linkov
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=E1RaTLh-0005Mt-Iu@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=cyd@gnu.org \
--cc=emacs-devel@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.