From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: order of manuals in Info...
Date: Tue, 27 Jan 2009 05:40:50 +0200 [thread overview]
Message-ID: <uab9ds9fh.fsf@gnu.org> (raw)
In-Reply-To: <00d601c98008$cbdea6b0$c2b22382@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <emacs-devel@gnu.org>
> Date: Mon, 26 Jan 2009 14:52:41 -0800
>
>
> > > 1. What is the ordering scheme used in emacs -Q for the
> > > Info manuals?
> >
> > They are ordered by (loose) topics, with the "main" manuals first.
>
> No problem with that.
>
> But what are the "main" manuals, besides the five I mentioned:
> Info, Emacs, Emacs FAQ, Emacs Lisp Intro, and Elisp?
None.
> The question was about the order of those manuals that follow the five main
> manuals I mentioned. What's the rationale?
There are only 4 groups of manuals after these 5: Editing modes,
Network features, Misc features, and Lisp libraries. Inside each
group, the manuals are ordered in alphabetic order. Editing modes is
first for obvious (I hope) reasons; Networking is before Misc for
likewise obvious reasons ("misc" should always be last); and libraries
are mainly for Lisp programmers, so they are last.
> Do you think the current order is the best one?
> Is there room for improvement?
There's always room for improvement, but I think the current order is
fine, and I think there are much more important problems to work on
now to help Emacs 23 be released sooner rather than later.
> And what about question #2: shortening the long lines?
Why is this so important? shorter description lose information. I
think the current descriptions strike a reasonably good balance.
prev parent reply other threads:[~2009-01-27 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 5:43 order of manuals in Info Drew Adams
2009-01-26 22:39 ` Eli Zaretskii
2009-01-26 22:52 ` Drew Adams
2009-01-27 3:40 ` Eli Zaretskii [this message]
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=uab9ds9fh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=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.