unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Info bug with @xref{Sample .emacs File, , , ccmode, the CC Mode Manual}.
Date: Mon, 12 Dec 2005 22:59:15 +0200	[thread overview]
Message-ID: <uk6ea9gm4.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1051212091512.422B-100000@acm.acm> (message from Alan Mackenzie on Mon, 12 Dec 2005 09:32:55 +0000 (GMT))

> Date: Mon, 12 Dec 2005 09:32:55 +0000 (GMT)
> From: Alan Mackenzie <acm@muc.de>
> Cc: emacs-devel@gnu.org
> 
> OK.  The warning in that manual is somewhat inconspicuous.  On the page
> "node" we have:
> 
>       To create a node, write an `@node' command at the beginning of a
>     line, and follow it with up to four arguments, separated by commas, on
>     the rest of the same line.
> 
> , with no mention of colons, parens or periods.  In the sub-node
> "Choosing Node and Pointer Names", there is no mention of the
> restriction.  Only in (the relatively obscurely named) "Node Line
> Requirements" is this restriction mentioned.  This seems suboptimal.

Did you try index search (the `i' command)?  There are at least two
index entries that should have helped you find this text in a blink:
"Period in nodename" and "Node names, invalid characters in".  Index
search is The Right Way of finding something in an Info manual quickly
and efficiently.

That said, if you think this information should be referenced from
less obscure places, please submit a bug report to the Texinfo
bug-reporting mailing list.

  reply	other threads:[~2005-12-12 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-11 18:37 Info bug with @xref{Sample .emacs File, , , ccmode, the CC Mode Manual} Alan Mackenzie
2005-12-11 19:58 ` Eli Zaretskii
2005-12-11 21:28   ` Alan Mackenzie
2005-12-12  0:58     ` Robert J. Chassell
2005-12-12  9:32       ` Alan Mackenzie
2005-12-12 20:59         ` Eli Zaretskii [this message]
2005-12-12  5:23     ` Richard M. Stallman
2005-12-12  5:39     ` Eli Zaretskii
2005-12-12 23:44       ` Karl Berry

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=uk6ea9gm4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.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).