From: karl@freefriends.org (Karl Berry)
Cc: juri@jurta.org, teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: automatic anchors for definition commands.
Date: Thu, 8 Jan 2004 12:24:12 -0500 [thread overview]
Message-ID: <200401081724.i08HOCd08186@f7.net> (raw)
In-Reply-To: <E1AeaN7-00078R-Ms@fencepost.gnu.org>
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.
A test with 2000 randomly-generated @anchors (the Elisp manual has about
1800 @def... cmds) ran fine, both for speed and space.
However, 5000 anchors overflows the string space in last year's TeX Live
distribution. (This year's has bigger maximums, as do a few other
distributions I tried.) None of the other various TeX capacities are a
problem, and speed isn't a problem either.
I think I could play with texinfo.tex and eliminate perhaps 1/3 of the
string space in common cases (by getting rid of empty -snt xrdef
values), if we want to pursue it.
next prev parent reply other threads:[~2004-01-08 17:24 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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200401081724.i08HOCd08186@f7.net \
--to=karl@freefriends.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).