unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-Xtra
Date: Thu, 13 Apr 2006 11:28:46 +0300	[thread overview]
Message-ID: <usloh3mm9.fsf@gnu.org> (raw)
In-Reply-To: <17469.29694.605871.59144@farnswood.snap.net.nz> (message from Nick Roberts on Thu, 13 Apr 2006 09:41:18 +1200)

> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Thu, 13 Apr 2006 09:41:18 +1200
> 
> I think emacs-Xtra is becoming a bit of a dog's breakfast

I tend to agree.

> (possibly an ms-dog's breakfast!).

I don't understand this part, especially since most of the MS-DOS info
is still in an appendix to the main manual.

> If I want to find something out about VC, I don't want
> to have to search through *two* manuals to find it because I can't guess
> where the arbitrary split has been made.
> 
> I think the all the documentation for VC should be in one manual.

I agree.  And the same goes for Calendar.

On top of that, whoever split portions of msdog.texi into emacs-xtra,
managed to remove from the main manual important information about
setting up printing on Windows.

> I have two suggestions:
> 
> 1) VC has its own manual like PCL-CVS does.
> 
> 2) All the programming/development topics are moved to a separate manual
>    (Emacs IDE?) and only the obscure stuff is left in emacs-Xtra.

I have a 3rd suggestion (which I think I already made in the past):

  3) Have those ``extra'' sections be part of the on-line manual, but
     not of the printed manual.  In the printed manual, replace the
     extra sections with an xref to the extra manual.  The Texinfo
     @ifinfo facility should do the trick.

This should be a good solution to the original problem, which is that
the FSF wants the printed manuals it sells to not be too large.

  parent reply	other threads:[~2006-04-13  8:28 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     ` emacs-Xtra Nic
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 ` Eli Zaretskii [this message]
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=usloh3mm9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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).