From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: juri@jurta.org, bob@rattlesnake.com, emacs-devel@gnu.org
Subject: Re: Info enhancements
Date: Sat, 6 Dec 2003 15:40:51 -0600 (CST) [thread overview]
Message-ID: <200312062140.hB6LepT09869@raven.dms.auburn.edu> (raw)
In-Reply-To: <200312061449.hB6Enaa16133@f7.net> (karl@freefriends.org)
Again, sorry for assuming the wrong author in my previous message,
falsely attributing quotes to Eli and misspelling Juri's name
repeatedly (again). Let us see how many blunders I manage to commit
in the present post.
This concerns the problem with the place references lead to in info.
As already mentioned, I believe that just going to the top of the node
is better than guessing at the risk of misleading the user.
The ideal would be to have a _reliable_ way to go to the correct place
without requiring any changes in existing .texi files. Since a
solution of this type is probably impossible, we should, in my
opinion, stick with the @anchor solution.
Juri's change requires rewriting references in .texi files in a way
that departs from the present standard style and I believe that Juri
mentioned himself in a previous post that his method is not 100%
reliable. Hence I would personally _not_ lean toward making this
particular change. This is, as I already pointed out before,
independent of the question of whether we adopt the other changes in
the patch.
But what do we want to do with @anchor? I have always actually
_avoided_ using it, because I saw it barely ever used in any major
manual. For instance, it is _only_ used in texinfo.txi to illustrate
the @anchor command itself and _never_ used in info.texi. I deduced
from this an implicit stylistic guideline "by example" that one should
use @anchor very sparingly, that is, only if *really* called for, and
that it would not be appropriate to write five or so @anchors per
node. If anchors are actually preferred over node names, unless the
top of the node is the _real_ target, that should be clearly pointed
out in texinfo.txi. Or one might give some guidelines on _when_ to use
@anchor.
If we started using @anchor systematically, the apparent inconsistency
with older Texinfo source might be confusing to the user. A reference
would lead in a random way either to the top of the node or to the
"correct place". At the very least, something should be said about it
in (info)Help-Xref.
Sincerely,
Luc.
next prev parent reply other threads:[~2003-12-06 21:40 UTC|newest]
Thread overview: 148+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 19:42 Info enhancements Karl Berry
2003-12-03 19:58 ` Robert J. Chassell
2003-12-04 7:07 ` Juri Linkov
2003-12-04 13:12 ` Robert J. Chassell
2003-12-04 15:29 ` Eli Zaretskii
2003-12-04 16:44 ` Karl Berry
2003-12-04 20:13 ` Robert J. Chassell
2003-12-06 21:01 ` Kai Grossjohann
2003-12-07 5:41 ` Eli Zaretskii
2003-12-07 14:49 ` Kai Grossjohann
2003-12-07 15:25 ` Eli Zaretskii
2003-12-07 16:42 ` Kai Grossjohann
2003-12-07 18:35 ` Eli Zaretskii
2003-12-08 19:28 ` Richard Stallman
2003-12-08 19:43 ` Stefan Monnier
2003-12-05 14:09 ` Juri Linkov
2003-12-05 14:26 ` Karl Berry
2003-12-05 15:57 ` Juri Linkov
2003-12-05 17:44 ` Eli Zaretskii
2003-12-06 0:15 ` Juri Linkov
2003-12-06 9:46 ` Eli Zaretskii
2003-12-05 18:02 ` Luc Teirlinck
2003-12-05 22:33 ` Luc Teirlinck
2003-12-05 22:36 ` Luc Teirlinck
2003-12-05 23:52 ` Juri Linkov
2003-12-06 9:43 ` Eli Zaretskii
2003-12-06 16:45 ` Luc Teirlinck
2003-12-06 17:15 ` Eli Zaretskii
2003-12-06 18:25 ` Luc Teirlinck
2003-12-07 17:19 ` Richard Stallman
2003-12-06 17:50 ` Luc Teirlinck
2003-12-07 0:23 ` Luc Teirlinck
2003-12-07 2:19 ` Luc Teirlinck
2003-12-07 2:31 ` Luc Teirlinck
2003-12-07 17:31 ` Juri Linkov
2003-12-07 17:44 ` Luc Teirlinck
2003-12-07 18:00 ` Luc Teirlinck
2003-12-07 18:32 ` Eli Zaretskii
2003-12-07 18:57 ` Luc Teirlinck
2003-12-07 19:27 ` Juri Linkov
2003-12-08 6:48 ` Eli Zaretskii
2003-12-08 6:45 ` Eli Zaretskii
2003-12-08 9:51 ` Juri Linkov
2003-12-09 3:34 ` Luc Teirlinck
2003-12-09 10:06 ` Eli Zaretskii
2003-12-10 2:56 ` Luc Teirlinck
2003-12-10 8:06 ` Eli Zaretskii
2003-12-10 3:03 ` Luc Teirlinck
2003-12-06 0:27 ` Juri Linkov
2003-12-07 17:19 ` Richard Stallman
2003-12-07 21:21 ` Juri Linkov
2003-12-08 6:58 ` Eli Zaretskii
2003-12-08 10:12 ` Juri Linkov
2003-12-08 10:29 ` Miles Bader
2003-12-08 10:46 ` Juri Linkov
2003-12-08 11:40 ` Eli Zaretskii
2003-12-08 14:09 ` Juri Linkov
2003-12-09 11:53 ` Kim F. Storm
2003-12-08 17:05 ` Luc Teirlinck
2003-12-09 10:08 ` Eli Zaretskii
2003-12-08 10:35 ` Eli Zaretskii
2003-12-05 18:27 ` Karl Berry
2003-12-05 20:44 ` Luc Teirlinck
2003-12-05 21:00 ` Luc Teirlinck
2003-12-06 9:11 ` Eli Zaretskii
2003-12-07 17:59 ` Juri Linkov
2003-12-06 1:27 ` Juri Linkov
2003-12-06 9:38 ` Eli Zaretskii
2003-12-07 15:43 ` Juri Linkov
2003-12-06 14:49 ` Karl Berry
2003-12-06 15:31 ` Eli Zaretskii
2003-12-06 21:40 ` Luc Teirlinck [this message]
2003-12-06 22:38 ` Luc Teirlinck
2003-12-07 5:45 ` Eli Zaretskii
2003-12-07 20:00 ` Juri Linkov
2003-12-08 6:56 ` Eli Zaretskii
2003-12-09 21:48 ` Richard Stallman
2003-12-07 17:19 ` Richard Stallman
2003-12-07 18:44 ` Luc Teirlinck
2003-12-07 19:00 ` Luc Teirlinck
2003-12-07 21:54 ` Juri Linkov
2003-12-07 22:01 ` Luc Teirlinck
2003-12-09 21:49 ` Richard Stallman
2003-12-08 19:28 ` Richard Stallman
2003-12-10 3:29 ` Luc Teirlinck
2003-12-10 15:48 ` Richard Stallman
2003-12-08 5:46 ` Luc Teirlinck
2003-12-08 17:34 ` Luc Teirlinck
2003-12-09 21:48 ` Richard Stallman
2003-12-04 15:50 ` Stefan Monnier
2003-12-05 0:11 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2003-12-07 1:20 Karl Berry
2003-12-07 5:50 ` Eli Zaretskii
2003-12-07 0:59 Karl Berry
2003-12-07 5:47 ` Eli Zaretskii
2003-12-07 13:42 ` Luc Teirlinck
2003-12-08 0:01 ` Kim F. Storm
2003-12-08 10:28 ` Juri Linkov
2003-12-09 21:48 ` Richard Stallman
2003-12-10 7:37 ` Eli Zaretskii
2003-12-11 14:45 ` Richard Stallman
2003-12-07 0:56 Karl Berry
2003-12-07 0:53 Karl Berry
2003-12-07 5:46 ` Eli Zaretskii
2003-12-06 19:36 Karl Berry
2003-12-06 19:53 ` Luc Teirlinck
2003-12-06 20:38 ` Luc Teirlinck
2003-12-06 20:30 ` Luc Teirlinck
2003-12-06 14:49 Karl Berry
2003-12-04 22:55 Karl Berry
2003-12-02 17:27 Info enhancements (was: Re: HTML as info format) Eli Zaretskii
2003-12-02 19:26 ` Karl Berry
2003-12-03 5:38 ` Info enhancements Juri Linkov
2003-12-03 13:27 ` Karl Berry
2003-12-03 15:46 ` Robert J. Chassell
2003-12-20 5:34 ` Juri Linkov
2003-12-20 14:57 ` Karl Berry
2003-12-01 10:38 Juri Linkov
2003-12-02 3:34 ` Luc Teirlinck
2003-12-02 10:54 ` Juri Linkov
2003-12-02 4:43 ` Luc Teirlinck
2003-12-02 21:22 ` Reiner Steib
2003-12-03 5:04 ` Juri Linkov
2004-09-01 16:42 ` Reiner Steib
2004-09-01 20:55 ` Juri Linkov
2004-09-02 19:02 ` Richard Stallman
2003-12-03 0:33 ` Kim F. Storm
2003-12-03 6:43 ` Juri Linkov
2003-12-12 2:08 ` Juri Linkov
2003-12-12 14:24 ` Karl Berry
2003-12-12 17:14 ` Eli Zaretskii
2003-12-12 19:23 ` Stefan Monnier
2003-12-13 10:12 ` Eli Zaretskii
2003-12-13 23:15 ` Richard Stallman
2003-12-12 21:38 ` Juri Linkov
2003-12-13 15:17 ` Richard Stallman
2003-12-16 2:14 ` Juri Linkov
2003-12-17 3:28 ` Richard Stallman
2003-12-18 3:03 ` Juri Linkov
2003-12-18 16:59 ` Richard Stallman
2003-12-19 14:03 ` Luc Teirlinck
2003-12-20 5:27 ` Juri Linkov
2003-12-13 15:48 ` Eli Zaretskii
2003-12-15 2:35 ` Richard Stallman
2003-12-15 6:01 ` Eli Zaretskii
2003-12-15 20:06 ` Richard Stallman
2003-12-16 3:00 ` Juri Linkov
2003-12-16 12:12 ` Kim F. Storm
2003-12-17 3:28 ` Richard Stallman
2003-12-17 3:28 ` 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
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=200312062140.hB6LepT09869@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=bob@rattlesnake.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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 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).