From: Andreas Schwab <schwab@suse.de>
Cc: "Kim F. Storm" <storm@cua.dk>, emacs-devel@gnu.org
Subject: Re: Hiding *Note:: "tags" in info files
Date: Wed, 30 Oct 2002 20:14:37 +0100 [thread overview]
Message-ID: <jeof9bwxgi.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.SUN.3.91.1021030161352.12714B-100000@is> (Eli Zaretskii's message of "Wed, 30 Oct 2002 16:14:33 +0200 (IST)")
Eli Zaretskii <eliz@is.elta.co.il> writes:
|> On Wed, 30 Oct 2002, Andreas Schwab wrote:
|>
|> > |> That would make sense in many places, but there are also places where
|> > |> the *Notes are already in a "sensible" textual scope such as
|> > |>
|> > |> See *Note Some Topic:: for details.
|> >
|> > This is actually broken to begin with. If used properly the xref commands
|> > in texinfo never generate such an output.
|>
|> Right. The correct usage ("See @ref...") produces "See *note...", with a
|> lower-case `n'.
The texinfo manual suggests to use @xref at start of sentence.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-10-30 19:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 11:49 Hiding *Note:: "tags" in info files Kim F. Storm
2002-10-30 13:20 ` Andreas Schwab
2002-10-30 14:14 ` Eli Zaretskii
2002-10-30 19:14 ` Andreas Schwab [this message]
2002-10-31 17:26 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-11-01 8:57 Kim F. Storm
2002-11-01 9:34 ` Karl Eichwalder
2002-10-29 12:03 Kim F. Storm
2002-10-29 17:11 ` Francesco Potorti`
2002-10-29 19:42 ` Eli Zaretskii
2002-10-30 17:17 ` Richard Stallman
2002-10-30 23:51 ` Kim F. Storm
2002-10-31 4:07 ` Karl Eichwalder
2002-10-31 4:24 ` Miles Bader
2002-10-31 6:00 ` Eli Zaretskii
2002-10-31 17:27 ` Richard Stallman
2002-11-01 0:10 ` Kim F. Storm
2002-11-01 2:24 ` Karl Eichwalder
2002-11-01 8:01 ` Eli Zaretskii
2002-11-01 15:30 ` Stefan Monnier
2002-11-01 23:22 ` Kim F. Storm
2002-11-02 8:08 ` 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=jeof9bwxgi.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=emacs-devel@gnu.org \
--cc=storm@cua.dk \
/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).