From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: Divergence in menu appearance between Emacs Info and standalone Info
Date: Fri, 6 Jun 2003 13:28:05 +0000 (UTC) [thread overview]
Message-ID: <m19OHGH-000IeAC@rattlesnake.com> (raw)
In-Reply-To: <buofzmo2cbr.fsf@mcspd15.ucom.lsi.nec.co.jp> (message from Miles Bader on 06 Jun 2003 11:02:00 +0900)
You're not making much sense here; how does the verbiage surrounding
traditional info xrefs help a novice writer understand Texinfo?
As far as I can see, many people are absorbing, often without
realizing it, the broken design model of HTML, and are not gaining a
sense of the importance of nodes.
When Buffer-menu-use-header-line is set to t, in the following, some
novices do not realize that they do not have to connect to the
Internet to see "Overview" and "Change Log", but that they are in
different manuals:
Patches are most welcome; if possible, please make them with `diff -c'
(see Overview.) and include `ChangeLog' entries (see Change Log.).
They think that `Overview' and `ChangeLog' are the node names.
I agree that there is a problem with fully formed parenthetical cross
references: too many parentheses.
The historical format moves the inner parentheses further away
from the outer parentheses, but does not look good:
(see *note Overview: (diffutils)Top.)
One advantage of the historical format is that it is obviously
different from the format used by `g' (Info-goto-node) and by a menu.
Perhaps the cross reference output formats should look more like the
menu format. Here is what I mean where `_' suggests the printed output
of @cite:
@xref{Indicating, , Indicating Definitions, texinfo, Texinfo Manual}.
In Info
when Buffer-menu-use-header-line is set to t:
See (texinfo)Indicating.
when Buffer-menu-use-header-line is set to nil:
See Indicating Definitions: (texinfo)Indicating.
In HTML: See <a href="texinfo.html#Indicating">Indicating Definitions</a>.
In XML with texinfo.dtd:
See
<xref>
<xrefnodename>Indicating</xrefnodename>
<xrefprinteddesc>Indicating Definitions</xrefprinteddesc>
<xrefinfofile>texinfo</xrefinfofile>
</xref>.
Printed: See "Indicating Definitions" in the _Texinfo Manual_.
(see @pxref{Indicating, , Indicating Definitions, texinfo, Texinfo Manual})
In Info
when Buffer-menu-use-header-line is set to t:
(see (texinfo)Indicating)
when Buffer-menu-use-header-line is set to nil:
(see Indicating Definitions: (texinfo)Indicating)
In HTML: (see <a href="texinfo.html#Indicating">Indicating Definitions</a>)
In XML with texinfo.dtd:
(see
<xref>
<xrefnodename>Indicating</xrefnodename>
<xrefprinteddesc>Indicating Definitions</xrefprinteddesc>
<xrefinfofile>texinfo</xrefinfofile>
</xref>)
Printed: (see "Indicating Definitions" in the _Texinfo Manual_)
and in a menu:
* Indicating Definitions: (texinfo)Indicating. How to indicate
definitions, files,
etc.
--
Robert J. Chassell Rattlesnake Enterprises
http://www.rattlesnake.com GnuPG Key ID: 004B4AC8
http://www.teak.cc bob@rattlesnake.com
next prev parent reply other threads:[~2003-06-06 13:28 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 14:04 Divergence in menu appearance between Emacs Info and standalone Info Karl Berry
2003-06-04 14:26 ` Miles Bader
2003-06-04 15:01 ` Stefan Monnier
2003-06-04 15:24 ` Eli Zaretskii
2003-06-04 15:31 ` Stefan Monnier
2003-06-04 16:55 ` Luc Teirlinck
2003-06-04 17:14 ` Stefan Monnier
2003-06-05 2:38 ` Luc Teirlinck
2003-06-05 3:23 ` Miles Bader
2003-06-05 5:52 ` Eli Zaretskii
2003-06-05 13:35 ` Stefan Monnier
2003-06-06 9:46 ` Eli Zaretskii
2003-06-06 11:28 ` Andreas Schwab
2003-06-06 15:38 ` Stefan Monnier
2003-06-05 5:49 ` Eli Zaretskii
2003-06-05 10:58 ` Richard Stallman
2003-06-04 15:25 ` Eli Zaretskii
2003-06-04 15:47 ` Luc Teirlinck
2003-06-05 10:57 ` Richard Stallman
2003-06-05 12:27 ` Robert J. Chassell
2003-06-06 0:11 ` Kim F. Storm
2003-06-05 22:55 ` Miles Bader
2003-06-05 23:11 ` Robert J. Chassell
2003-06-05 23:23 ` Stefan Monnier
2003-06-05 23:56 ` Robert J. Chassell
2003-06-06 2:02 ` Miles Bader
2003-06-06 13:28 ` Robert J. Chassell [this message]
2003-06-06 9:50 ` Eli Zaretskii
2003-06-06 13:02 ` David Kastrup
2003-06-08 1:09 ` Richard Stallman
2003-06-08 1:20 ` Stefan Monnier
2003-06-08 2:30 ` David Kastrup
2003-06-09 8:53 ` Richard Stallman
2003-06-06 14:00 ` Robert J. Chassell
2003-06-06 15:51 ` Eli Zaretskii
2003-06-06 16:54 ` Robert J. Chassell
2003-06-06 17:25 ` Kevin Rodgers
2003-06-08 1:07 ` Richard Stallman
2003-06-15 15:47 ` Karl Eichwalder
2003-06-15 16:08 ` Stefan Monnier
2003-06-15 22:27 ` Miles Bader
2003-06-16 12:02 ` Reiner Steib
2003-06-16 18:45 ` Robert J. Chassell
2003-06-15 17:46 ` Robert J. Chassell
2003-06-16 5:46 ` Karl Eichwalder
2003-06-15 19:00 ` Kai Großjohann
2003-06-06 17:24 ` Kevin Rodgers
2003-06-07 11:46 ` Kai Großjohann
2003-06-06 17:03 ` Richard Stallman
2003-06-05 16:50 ` Kai Großjohann
2003-06-05 20:50 ` Luc Teirlinck
2003-06-06 16:05 ` Luc Teirlinck
2003-06-06 16:29 ` Luc Teirlinck
-- strict thread matches above, loose matches on Subject: below --
2003-06-09 23:17 Karl Berry
2003-06-11 0:24 ` Richard Stallman
2003-06-08 13:48 Karl Berry
2003-06-08 16:02 ` Eli Zaretskii
2003-06-09 23:00 ` Richard Stallman
2003-06-05 16:30 Karl Berry
2003-06-05 16:44 ` Luc Teirlinck
2003-06-05 23:39 ` Kim F. Storm
2003-06-06 17:03 ` Richard Stallman
2003-06-05 12:59 Karl Berry
2003-06-05 15:52 ` Luc Teirlinck
2003-06-05 16:23 ` Luc Teirlinck
2003-06-05 18:19 ` Luc Teirlinck
2003-06-06 17:02 ` Richard Stallman
2003-06-04 23:12 Karl Berry
2003-06-05 0:39 ` Luc Teirlinck
2003-06-04 8:54 Richard Stallman
2003-06-04 9:06 ` Miles Bader
2003-06-04 15:12 ` Andreas Schwab
2003-06-04 21:54 ` David Kastrup
2003-06-12 6:47 ` Karl Eichwalder
2003-06-12 22:13 ` Luc Teirlinck
2003-06-13 3:58 ` Karl Eichwalder
2003-06-13 5:00 ` Luc Teirlinck
2003-06-13 5:10 ` Luc Teirlinck
2003-06-13 6:16 ` Stefan Monnier
2003-06-05 2:47 ` Kim F. Storm
2003-06-05 13:04 ` Andreas Schwab
2003-06-10 0:03 ` Kim F. Storm
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=m19OHGH-000IeAC@rattlesnake.com \
--to=bob@rattlesnake.com \
/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.