all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@elta.co.il>
Cc: juri@jurta.org, emacs-devel@gnu.org, karl@freefriends.org
Subject: Re: automatic anchors for definition commands.
Date: 08 Jan 2004 16:14:26 +0200	[thread overview]
Message-ID: <u1xqa5xz1.fsf@elta.co.il> (raw)
In-Reply-To: <200401080001.i0801xt11013@raven.dms.auburn.edu> (message from Luc Teirlinck on Wed, 7 Jan 2004 18:01:59 -0600 (CST))

> Date: Wed, 7 Jan 2004 18:01:59 -0600 (CST)
> From: Luc Teirlinck <teirllm@dms.auburn.edu>
> 
>    And as Eli says, sometimes reading from the beginning of the node
>    is better.
> 
> In those cases I _do_ refer to the top of the node.  I do not
> _automatically_ make anchor references because a function or variable
> name is mentioned.

The point is, the author of the manual does not always know what's
best; it depends on the reader.

> The entire section `(elisp)Related Topics' consists of references to
> definitions that are given in other chapters, but could quite as well
> have been given in the functions chapter.

I think such cases are relatively rare, even in the Emacs manuals,
where we use that to keep the sheer size of the manuals at bay.  It's
not clear to me whether we should draw too general conclusions from
these cases.  Again, this my opinion is not very strong.

      parent reply	other threads:[~2004-01-08 14:14 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
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 [this message]

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=u1xqa5xz1.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.