unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: eliz@gnu.org, emacs-devel@gnu.org, karl@freefriends.org
Subject: Re: Info - some notes about customization
Date: Sun, 05 Dec 2004 20:31:24 +0200	[thread overview]
Message-ID: <87mzwstx4z.fsf@jurta.org> (raw)
In-Reply-To: <075201c4d9a0$9e3d0390$0200a8c0@sedrcw11488> (Lennart Borgman's message of "Sat, 4 Dec 2004 01:00:49 +0100")

"Lennart Borgman" <lennart.borgman.073@student.lu.se> writes:
> On the Info start page in the part "Important General Concepts" I think
> "Command Arguments" is a bit misleading. A little bit up there is a node
> called "Commands" and those names are too close in my opinion. I would
> suggest renaming the first one to "Command Line Options".

The node "Command Arguments" can't be renamed because then the
standalone Info reader will fail to find this node with its
-O, --show-options, --usage option.

It looks for the following names:

    "%s invocation",
    "Invoking %s",
    "Preliminaries",	/* m4 has Invoking under Preliminaries! */
    "Invocation",
    "Command Arguments",/* Emacs */
    "Invoking `%s'",
    "%s options",
    "Options",
    "Option ",		/* e.g. "Option Summary" */
    "Invoking",
    "All options",	/* tar, paxutils */
    "Arguments",
    "%s cmdline",	/* ar */
    "%s",		/* last resort */

and will find a completely irrelevant node when the
"Command Arguments" node becomes renamed to something else.

Maybe the node name should be changed in the standalone Info reader
as well, but such a change is still not backward compatible.

-- 
Juri Linkov
http://www.jurta.org/emacs/

  reply	other threads:[~2004-12-05 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04  0:00 Info - some notes about customization Lennart Borgman
2004-12-05 18:31 ` Juri Linkov [this message]
2004-12-05 20:51   ` Eli Zaretskii
2004-12-06  1:40   ` 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=87mzwstx4z.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=karl@freefriends.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).