unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nic <nferrier@tapsellferrier.co.uk>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: emacs-Xtra
Date: Thu, 13 Apr 2006 08:10:16 +0100	[thread overview]
Message-ID: <87ek02t0h3.fsf@nicferrier.tapsellferrier.co.uk> (raw)
In-Reply-To: <17469.53282.265431.557135@farnswood.snap.net.nz> (Nick Roberts's message of "Thu, 13 Apr 2006 16:14:26 +1200")

Nick Roberts <nickrob@snap.net.nz> writes:

>  >     2) All the programming/development topics are moved to a separate manual
>  >        (Emacs IDE?) and only the obscure stuff is left in emacs-Xtra.
>  > 
>  > If this means splitting the Emacs Manual into two manuals, both of which
>  > we would print, maybe that is a good idea--but how would we split it?
>
> In such a way that that fairly self contained topics like VC stay together.
> You declined to say how much smaller the Emacs Manual needs to be, but I would
> keep as much in it as possible.
>
> Without this information, I would guess that the Avanced Features section could
> be Volume Two and everything before, and everything after (Recovery from
> Problems), could be Volume One.
>
>  > (Version control is not used solely for editing programs, so including
>  > VC in a manual for "editing programs with Emacs" would not be right.)
>
> Emacs User Manaual Vol 1: Basics
> Emacs User Manaual Vol 2: Advanced Features

How about just publishing an extra manual with the information in it
needed for programmers?

I'm sure we could find a whole lot more to put in that - and maybe
trim down the Emacs manual. 

So: there would be duplication (vc information in both) but one would
be able to control that with texinfo builds.


Nic Ferrier

  reply	other threads:[~2006-04-13  7:10 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12 21:41 emacs-Xtra Nick Roberts
2006-04-13  3:20 ` emacs-Xtra Richard Stallman
2006-04-13  4:14   ` emacs-Xtra Nick Roberts
2006-04-13  7:10     ` Nic [this message]
2006-04-13  9:02       ` emacs-Xtra Eli Zaretskii
2006-04-14  4:18       ` emacs-Xtra Richard Stallman
2006-04-14 22:21         ` emacs-Xtra Nic
2006-04-15 17:33           ` emacs-Xtra Richard Stallman
2006-04-13 18:40     ` emacs-Xtra Ted Zlatanov
2006-04-14  7:43       ` emacs-Xtra Eli Zaretskii
2006-04-14 13:39         ` emacs-Xtra Ted Zlatanov
2006-04-14 14:40           ` emacs-Xtra Eli Zaretskii
2006-04-14 16:05             ` emacs-Xtra Ted Zlatanov
2006-04-14 16:54               ` emacs-Xtra Eli Zaretskii
2006-04-15 17:32               ` emacs-Xtra Richard Stallman
2006-04-15 18:09                 ` emacs-Xtra David Kastrup
2006-04-18 15:03                 ` emacs-Xtra Ted Zlatanov
2006-04-19  4:17                   ` emacs-Xtra Richard Stallman
2006-04-19 16:34                     ` emacs doc changes (was: emacs-Xtra) Ted Zlatanov
2006-04-19 17:38                       ` emacs doc changes Ted Zlatanov
2006-04-19 17:51                       ` emacs doc changes (was: emacs-Xtra) Eli Zaretskii
2006-04-19 17:57                         ` emacs doc changes David Kastrup
2006-04-19 18:01                           ` Ted Zlatanov
2006-04-19 18:15                             ` David Kastrup
2006-04-19 18:34                               ` Giorgos Keramidas
2006-04-19 20:44                                 ` Stefan Monnier
2006-04-20  9:50                                   ` Eli Zaretskii
2006-04-20  9:58                                     ` David Kastrup
2006-04-20 10:13                                       ` Eli Zaretskii
2006-04-20 19:38                                         ` Richard Stallman
2006-04-20 21:09                                           ` Stefan Monnier
2006-04-27 14:42                                             ` Richard Stallman
2006-04-30 15:29                                               ` Stefan Monnier
2006-05-01  4:19                                                 ` Richard Stallman
2006-05-01 12:39                                                   ` Stefan Monnier
2006-05-02  2:05                                                     ` Richard Stallman
2006-05-11 23:06                                                       ` Aaron S. Hawley
2006-04-20 10:25                               ` Eli Zaretskii
2006-04-20  1:14                           ` Richard Stallman
2006-04-20 13:43                             ` Jay Belanger
2006-04-20  9:15                           ` Eli Zaretskii
2006-04-20  9:21                             ` David Kastrup
2006-04-19 17:58                         ` Ted Zlatanov
2006-04-25 16:48                           ` Richard Stallman
2006-04-15 17:32           ` emacs-Xtra Richard Stallman
2006-04-14 16:15       ` emacs-Xtra Richard Stallman
2006-04-14  4:18     ` emacs-Xtra Richard Stallman
2006-04-13  8:28 ` emacs-Xtra Eli Zaretskii
2006-04-13 18:40   ` emacs-Xtra Glenn Morris
2006-04-14  7:35     ` emacs-Xtra Eli Zaretskii
2006-04-14  4:18   ` emacs-Xtra Richard Stallman
2006-04-14  8:16     ` emacs-Xtra Eli Zaretskii
2006-04-21 11:43     ` emacs-Xtra Eli Zaretskii
2006-04-21 21:05       ` emacs-Xtra Richard Stallman
2006-04-14  4:18   ` emacs-Xtra 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=87ek02t0h3.fsf@nicferrier.tapsellferrier.co.uk \
    --to=nferrier@tapsellferrier.co.uk \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).