unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: New .texi file
Date: Tue, 15 Jun 2004 21:56:29 -0500 (CDT)	[thread overview]
Message-ID: <200406160256.i5G2uT019583@raven.dms.auburn.edu> (raw)
In-Reply-To: <87smcztob4.fsf@mail.jurta.org> (message from Juri Linkov on Sun,  13 Jun 2004 19:28:31 +0300)

Juri Linkov wrote:

   For example, the Autotype manual should be placed also into this new
   Emacs-X manual since Autotype is the only manual that doesn't describe
   a separate package.

I personally do not believe so.  The idea is that the main source of
information about Emacs is the Emacs manual.  (Or the Elisp manual for
Elisp programmers.)  Then comes browsing packages using `C-h p' and
browsing user options using Custom.  Then any collection of features
that logically can be grouped into something large and coherent enough
can get their own manual.  There are things that are not suitably
covered by any of these categories.  They are too small to motivate
all the extra work one has to do (and extra know-how one may have to
acquire) to commit a new manual rather than just add nodes to a
pre-existing manual.  Also, if one would get too many of such
"micro-manuals", then they would also unnecessarily clutter the user's
dir file.  (A problem that is already bad enough right now.)  That is
what the new manual is intended for.

Sections 1-8 of Autotype essentially cover things related to the
skeleton machinery.  Sections 9-12 look somewhat out of place, but not
too badly.  Sections 11-12 refer to `Commentary' sections for more
details.  Section 10 probably should too.  It is not the intended
purpose of the new manual to duplicate information obtainable through
`C-h p'.

Sincerely,

Luc.

  reply	other threads:[~2004-06-16  2:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-13  1:18 New .texi file Luc Teirlinck
2004-06-13 11:47 ` Kai Grossjohann
2004-06-13 16:28 ` Juri Linkov
2004-06-16  2:56   ` Luc Teirlinck [this message]
2004-06-13 22:21 ` Kim F. Storm
2004-06-14  3:06   ` Luc Teirlinck
2004-06-14  7:39     ` Kim F. Storm
2004-06-14 19:44       ` Luc Teirlinck
2004-06-14 19:52     ` Eli Zaretskii
2004-06-15 18:13     ` 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=200406160256.i5G2uT019583@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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).