unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Emacs Manual topics to remove?
Date: Tue, 14 Mar 2006 07:18:14 -0800	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICEELCDDAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1FJ6eR-0008TG-Qp@fencepost.gnu.org>

        * all mail stuff and all news stuff (including gnus)
        * all calendar and diary stuff
        * version contol (maybe)
        * all language modes: C, Fortran, Tex, Nroff, ASM, ...
        * running debuggers (GUD)
        * international stuff
        * AntiNews

    That would be too drastic.

What would be too drastic? To consider them as _candidates_?

    Most of that is very important, and worth printing in the manual.

Of course it is. And not only most of it, but all of it.

I certainly was not proposing moving all of that (or even any of it) out of
the printed manual. And I made it clear that these topics could be looked at
after those that had already been proposed by others had been considered. As
I said, these are _additional_ candidates to consider, if need be.

You asked for candidates. These important topics are nevertheless less
fundamental than basic editing and such, which is the point. If only one or
two obvious candidates are proposed, that doesn't help if the intention or
need is to move more material. Given a long list, you can prioritize it and
pick those least important to move, as space permits. A list that is too
short is no help in moving more material.

You didn't say that enough had already been moved, after moving emerge,
picture, and Fortran. The implication was that you were still looking for
more (how much?) to move. Of the topics that remained and hadn't yet been
suggested (and were not trivially small), I listed the least fundamental
(IMO) as additional candidates.

You didn't make the requirement clear, if you had in mind a particular amout
of material to move. Lacking that, the most appropriate response to your
request would be a prioritized list of _all_ of the manual nodes.

  reply	other threads:[~2006-03-14 15:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-12 15:45 Emacs Manual topics to remove? Richard Stallman
2006-03-12 20:26 ` Chong Yidong
2006-03-12 22:24   ` Nick Roberts
2006-03-13  0:23     ` Chong Yidong
2006-03-13  9:32       ` Miles Bader
2006-03-13  9:55         ` Nick Roberts
2006-03-13 18:53           ` Luc Teirlinck
2006-03-13 20:46             ` Nick Roberts
2006-03-13 22:41           ` Richard Stallman
2006-03-13 22:41         ` Richard Stallman
2006-03-13 22:41         ` Richard Stallman
2006-03-13 16:07       ` Randal L. Schwartz
2006-03-13 17:06         ` Drew Adams
2006-03-13 17:22           ` Chip Coldwell
2006-03-13 22:59           ` Miles Bader
2006-03-13 23:50             ` Lennart Borgman
2006-03-14 10:21           ` Richard Stallman
2006-03-14 15:18             ` Drew Adams [this message]
2006-03-14 17:46               ` Richard Stallman
2006-03-13 10:06     ` Romain Francoise
2006-03-13 12:55     ` Richard Stallman
2006-03-13 12:55   ` Richard Stallman
2006-03-16  3:27     ` Chong Yidong
2006-03-16 20:19       ` Richard Stallman
2006-03-12 23:14 ` Jesper Harder
2006-03-13 12:55   ` 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=DNEMKBNJBGPAOPIJOOICEELCDDAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    /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).