From: Glenn Morris <rgm@gnu.org>
To: Nic Ferrier <nferrier@ferrier.me.uk>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, emacs-devel@gnu.org
Subject: Re: ELPAing all the GNU manuals
Date: Sun, 28 Sep 2014 16:58:57 -0400 [thread overview]
Message-ID: <njfvfb1my6.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87iok7txrv.fsf@ferrier.me.uk> (Nic Ferrier's message of "Sun, 28 Sep 2014 19:17:40 +0100")
Nic Ferrier wrote:
> I am an Ubuntu user. I just installed gnupg. No info manual appeared
> in my Emacs.
The manuals are often packaged separately. You need to install
gnupg-doc, which is i) a suggested package of the gnupg package; and ii)
guaranteed to match the version of gnupg you have installed (how would
your method deal with that - package multiple versions of every manual?)
It shows up in my Emacs just fine (Ubuntu 14.04) with no configuration
needed.
> But I re-assert that is a problem. If "because we can doesn't mean we
> should" is a gateway to ELPA then you've got a problem.
AFAICS Stefan takes a very inclusive approach with elpa.gnu.org.
Your specific proposal just doesn't seem to make much sense.
next prev parent reply other threads:[~2014-09-28 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 9:36 ELPAing all the GNU manuals Nic Ferrier
2014-09-28 10:47 ` Alan Mackenzie
2014-09-28 11:06 ` David Kastrup
2014-09-28 11:10 ` Nic Ferrier
2014-09-28 12:12 ` joakim
2014-09-28 12:41 ` David Kastrup
2014-09-28 12:48 ` Alan Mackenzie
2014-09-28 12:49 ` Eric Brown
2014-09-28 16:37 ` Stefan Monnier
2014-09-28 18:17 ` Nic Ferrier
2014-09-28 20:58 ` Glenn Morris [this message]
2014-09-29 10:32 ` Thomas Koch
2014-09-29 16:51 ` Nic Ferrier
2014-09-29 20:49 ` Richard Stallman
2014-09-29 12:34 ` Matthias Meulien
2014-09-29 13:25 ` Eli Zaretskii
2014-09-29 19:35 ` Matthias Meulien
2014-09-29 20:00 ` Eli Zaretskii
2014-09-29 20:47 ` 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=njfvfb1my6.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=nferrier@ferrier.me.uk \
/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.