all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "Eli Zaretskii" <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: RE: doc of eval-defun (C-M-x)
Date: Tue, 10 Jul 2007 09:19:28 -0700	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICKEOPDNAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1I8HwZ-0001zJ-AA@fencepost.gnu.org>

> >    Nodes `Defining Variables'
> >    and `Variable Definitions' should be indexed for `eval-defun'.
>
> Can you explain why?  `eval-defun' is fully described in the Emacs
> manual (and indexed there), so why would we need to describe it again
> in the ELisp manual?

It's already described in the Elisp manual. I'm asking that the existing
description be indexed.

As to explaining why it should be indexed, that explanation is now
irrelevant, unfortunately, since RMS has said:

> We don't use the index that way.

Nevertheless, FWIW, my thinking was that, since `eval-defun' is discussed in
that node, and this use of `eval-defun' is as common as the `edebug' use
(IMO), it would be good to help readers find the discussion of `eval-defun'
in the context of `defvar' and `defcustom' (and `defface' as well). We index
the edebug discussion of `eval-defun'; we should also index the use with
`C-M-x', which is just as common.

This is in the Elisp manual presumably because Emacs-Lisp programmers are
interested in it, and indexing it helps them find it. IMO, Emacs-Lisp
programmers are also those most likely to use `C-M-x' (`eval-defun').

  reply	other threads:[~2007-07-10 16:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 22:30 doc of eval-defun (C-M-x) Drew Adams
2007-07-10  5:38 ` Richard Stallman
2007-07-10 15:48 ` Eli Zaretskii
2007-07-10 16:19   ` Drew Adams [this message]
2007-07-10 20:08     ` Eli Zaretskii
2007-07-10 21:58       ` Drew Adams
2007-07-11  3:05       ` Richard Stallman

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=DNEMKBNJBGPAOPIJOOICKEOPDNAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=bug-gnu-emacs@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.