From: "Paul W. Rankin" <hello@paulwrankin.com>
To: rms@gnu.org
Cc: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
Subject: Re: Function to retrieve package version
Date: Wed, 22 May 2019 12:02:20 +1000 [thread overview]
Message-ID: <m2imu3mekz.fsf@paulwrankin.com> (raw)
In-Reply-To: <E1hTBDQ-00024B-8S@fencepost.gnu.org>
On Wed, May 22 2019, Richard Stallman wrote:
> Please don't do that. The manual is very long already. That
> makes
> printing expensive. Before we add a new topic, we need to
> consider
> whether the benefit is worth the increase in cost.
Can you elaborate on what you mean here Richard? Do you mean
people printing the Elisp manual themselves, or does the FSF print
copies of the Elisp manual gratis?
If the former, surely the benefit of Emacs Lisp package
maintainers knowing about the built-in "utility functions for
Emacs Lisp maintainers" outweighs the miniscule additional cost of
a couple of paragraphs that might add a single page to the printed
output, which at the very most (barring some sort of OCD
condition) will be printed once per major release?
And if I'm going to the trouble/expense of printing the entire
Elisp manual, I damn sure want it to be as complete as possible,
rather than later discover it's missing key topics and so will
require a reprint. The idea that I'm being miserly about my stock
of printer paper in this scenario is a little unrealistic...
next prev parent reply other threads:[~2019-05-22 2:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 4:55 Function to retrieve package version Paul W. Rankin
2019-05-21 8:32 ` Michael Albinus
2019-05-21 9:08 ` Paul W. Rankin
2019-05-21 9:40 ` Michael Albinus
2019-05-21 20:18 ` Richard Stallman
2019-05-22 2:02 ` Paul W. Rankin [this message]
2019-05-22 2:26 ` Eli Zaretskii
2019-05-22 2:49 ` Paul W. Rankin
2019-05-22 7:49 ` Michael Albinus
2019-05-22 7:50 ` Eli Zaretskii
2019-05-22 22:39 ` Richard Stallman
2019-05-21 21:55 ` Stefan Monnier
2019-05-21 22:56 ` Eric Abrahamsen
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=m2imu3mekz.fsf@paulwrankin.com \
--to=hello@paulwrankin.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--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).