From: Eli Zaretskii <eliz@elta.co.il>
Cc: juri@jurta.org, karl@freefriends.org, emacs-devel@gnu.org
Subject: Re: automatic anchors for definition commands.
Date: 07 Jan 2004 08:48:22 +0200 [thread overview]
Message-ID: <u3casb6fd.fsf@elta.co.il> (raw)
In-Reply-To: <200401070250.i072oJC09935@raven.dms.auburn.edu> (message from Luc Teirlinck on Tue, 6 Jan 2004 20:50:19 -0600 (CST))
> Date: Tue, 6 Jan 2004 20:50:19 -0600 (CST)
> From: Luc Teirlinck <teirllm@dms.auburn.edu>
>
> A larger and larger percentage of these anchors is starting to refer
> to function and variable definitions. There are _many_ nodes (or
> parts of nodes), say `(elisp)Related Topics', section 12.11 in the
> printed manual, that are index-like lists of references to function
> and variable definitions. Unlike the "real" indices, they do not
> refer to the page numbers _of the definitions_ in the printed manual.
> (They refer to the beginning of the section, which can be several
> pages off.)
Note that in some case, this might be actually a good idea: reading
from the section beginning might give you a broader perspective on the
subject.
I don't have a firm opinion on the automatic anchoring you suggest; at
first glance, it sounds like a lot of work for a relatively small
benefit.
next prev parent reply other threads:[~2004-01-07 6:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 2:50 automatic anchors for definition commands Luc Teirlinck
2004-01-07 6:48 ` Eli Zaretskii [this message]
2004-01-07 21:34 ` Karl Berry
2004-01-08 0:01 ` Luc Teirlinck
2004-01-08 0:20 ` Karl Berry
2004-01-08 0:32 ` Luc Teirlinck
2004-01-08 13:38 ` Richard Stallman
2004-01-08 17:24 ` Karl Berry
2004-01-09 11:46 ` Richard Stallman
2004-01-10 5:23 ` Luc Teirlinck
2004-01-11 19:37 ` Richard Stallman
2004-01-08 14:14 ` Eli Zaretskii
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=u3casb6fd.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=karl@freefriends.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.