all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-Xtra
Date: Fri, 14 Apr 2006 17:40:19 +0300	[thread overview]
Message-ID: <umzeo1ar0.fsf@gnu.org> (raw)
In-Reply-To: <4nek002s4h.fsf@asimov.bwh.harvard.edu> (message from Ted Zlatanov on Fri, 14 Apr 2006 09:39:42 -0400)

> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Fri, 14 Apr 2006 09:39:42 -0400
> 
> On 14 Apr 2006, eliz@gnu.org wrote:
> 
> > Dividing the manual into 2 volumes doesn't solve the problem which is
> > the main cause for trying to keep the manual's size down.  The main
> > cause is that a larger manual increases the price of printing the
> > books, and thus makes it harder for the FSF to publish new versions.
> > (I'm guessing that publishing 2 volumes will increase the price even
> > more.)
> 
> By the same reasoning the FSF should not publish a two-part ELisp
> reference manual, because half of it could be online and it's cheaper
> to publish one book.

You are driving the arguments to absurd, which doesn't help to resolve
the issue in a reasonable way.

ELisp manual is larger than the Emacs user's manual because it needs
to cover more material.  It is impossible to make the ELisp manual
significantly shorter without omitting stuff that Lisp programmers
undoubtfully need to know.

The price of publishing is not the _only_ consideration.  The manual
is published first and foremost to cover the important parts of the
material; but it doesn't have to cover _everything_.  The distinction
between _enough_ and _everything_ is where the price comes into
consideration.  I'm sure you understand all this very well.

> I think that's false reasoning.

That's the reasoning I got from Richard, and I'll let him restate or
revise it (in the latter case, I apologize for possible confusion).

> If the price is prohibitive, let the FSF decide *that*, but Emacs
> certainly contains enough for two and even three manuals, so we
> should not start with the assumption that we have to have a smaller
> manual.

I didn't start with such an assumption, AFAIK the FSF has _already_
decided that the manuals should not grow too much.  We need to find a
practical way to include more stuff in the on-line manual, while not
enlarging the expenses of the printed version too much.

I hope the solution I suggested elsewhere in this thread will be
accepted as a reasonable compromise.

  reply	other threads:[~2006-04-14 14:40 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           ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=umzeo1ar0.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 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.