all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: order of manuals in Info...
Date: Sun, 25 Jan 2009 21:43:56 -0800	[thread overview]
Message-ID: <007501c97f79$14a0c260$0200a8c0@us.oracle.com> (raw)

1. What is the ordering scheme used in emacs -Q for the Info manuals?

If it's supposed to reflect general usefulness or popularity, then I would
expect to see things like Dired-X, Ediff, and Tramp higher up, and things like
Newsticker lower down. That's not a great way to organize the menu anyway (and
one person's useful is another's useless).

Simplest would be alphabetical order - easy to find most entries. But keep Info,
Emacs, Emacs FAQ, Emacs Lisp Intro, and Elisp at the top.

2. Why does the description of Emacs Lisp Intro appear on a separate line from
the menu item? (It is the same length as EasyPG Assistant, so it shouldn't be a
problem of item length.)

3. How about reducing the descriptions of these entries?

. VIPER from 3 lines to 1:
  VIPER    - VI emulation mode"

. SC, Autotype, Forms, and Widget descriptions from 2 lines to 1:
  SC       - Supercite: cite parts of messages
  Autotype - Automatically insert text you type often
  Forms    - Edit databases by filling in forms
  Widget   - UI toolkit used by Customize

The multiple-line descriptions can give a false impression of separating the
menu items into groups.
  






             reply	other threads:[~2009-01-26  5:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-26  5:43 Drew Adams [this message]
2009-01-26 22:39 ` order of manuals in Info Eli Zaretskii
2009-01-26 22:52   ` Drew Adams
2009-01-27  3:40     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='007501c97f79$14a0c260$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.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 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.