unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: emacs-devel@gnu.org
Subject: Re: texinfo-all-menus-update
Date: Mon, 18 Feb 2002 15:51:21 +0000 (UTC)	[thread overview]
Message-ID: <m16cq4X-000IeRC@localhost> (raw)
In-Reply-To: <20020205.090225.69697435.wl@gnu.org> (message from Werner LEMBERG on Tue, 05 Feb 2002 09:02:25 +0100 (CET))

    >>    Is there any reason why texinfo-all-menus-update produces
    >>    trailing whitespace after the menu entries?
    >>
    >> No reason.  It is a bug.  I never noticed it doing that, and am
    >> glad you found it.  I dislike trailing whitespace.

On looking at it again, I found the reason for the trailing whitespace
after the menu entries (or at least one of the reasons).
The whitespace is intended as a feature.

The whitespace is designed to make it easier to write a descriptive
phrase or sentence that explains what the node is about, either
directly or with the help of the `texinfo-start-menu-description'
command.  You start the description after the whitespace, which
provides an indent to a specificed column, so all your descriptions
are lined up.

(See the Texinfo Info File,
    Node: Menu Parts, and Node: Inserting; 
or the printed Texinfo Manual Section: 
    `The Parts of a Menu' and `Inserting Frequently Used Commands'.)

In general, menus should contain descriptions, even though technically
they are optional.  This is because node names and section titles are
often too short to explain the node well.

The whitespace comes from the `texinfo-insert-menu' command which, as
its documentation says,

    Indents the first line of the description, if any, to the value of
    texinfo-column-for-description.

The `texinfo-all-menus-update', `texinfo-master-menu', and
`texinfo-make-menu' commands all call the `texinfo-insert-menu'
command.  Also, they automatically incorporate the descriptions from
pre-existing menus, if they exist.

The design question is whether `texinfo-all-menus-update' should make
it easier to add descriptions to menu entries that lack them; or
whether the command should make it easier to avoid adding such
descriptions.

I favor menu entries with descriptions.  Consequently, I have changed
my mind and suggest treating the current functionality as a feature
rather than as a bug.

As you work on a Texinfo document, you can remove all trailing
whitespace with the `delete-trailing-whitespace' command.  (For
convenience I have bound a function key to that command; I use it 
frequently.)

-- 
    Robert J. Chassell                  bob@rattlesnake.com
    Rattlesnake Enterprises             http://www.rattlesnake.com

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  parent reply	other threads:[~2002-02-18 15:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020205.090225.69697435.wl@gnu.org>
2002-02-07  9:21 ` texinfo-all-menus-update Robert J. Chassell
2002-02-17 15:56   ` calendar: trailing whitespace (Re: texinfo-all-menus-update) Karl Eichwalder
2002-02-17 17:45     ` Karl Eichwalder
2002-02-18 15:51 ` Robert J. Chassell [this message]
2002-02-19 21:31   ` texinfo-all-menus-update 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=m16cq4X-000IeRC@localhost \
    --to=bob@rattlesnake.com \
    --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).