From: Richard Stallman <rms@gnu.org>
Cc: juri@jurta.org, teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: automatic anchors for definition commands.
Date: Thu, 08 Jan 2004 08:38:49 -0500 [thread overview]
Message-ID: <E1AeaN7-00078R-Ms@fencepost.gnu.org> (raw)
In-Reply-To: <200401080020.i080KMw16314@f7.net> (karl@freefriends.org)
However, I'm now somewhat convinced that adding implicit anchors for
definition commands, as we add index entries now, would be reasonable.
This would mean a tremendous increase in the number of names defined
for cross-referencing. That could cause a slowdown in TeX, or even
cause TeX to run out of memory. I think we should not do this.
I believe there are only three conclusions to be made at the present
stage. Either
(A) conclude that definitions stand out clearly enough anyway and
_only_ make anchors of type (3), which ofen refer to unnamed
pieces of text that do not stand out very clearly from the
surrounding text (but could not possibly be made into separate
nodes).
or make automatic anchors, either
(B) only for definitions
or
(C) for all index entries. If I remember well, Juri at one point
I prefer (D): continue handling this the way we do it now.
next prev parent reply other threads:[~2004-01-08 13:38 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 [this message]
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=E1AeaN7-00078R-Ms@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=teirllm@dms.auburn.edu \
/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.