From: Michael Albinus <michael.albinus@gmx.de>
To: "Paul W. Rankin" <hello@paulwrankin.com>
Cc: Eli Zaretskii <eliz@gnu.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Function to retrieve package version
Date: Wed, 22 May 2019 09:49:36 +0200 [thread overview]
Message-ID: <87ef4r6i9b.fsf@gmx.de> (raw)
In-Reply-To: m2ftp7mcey.fsf@paulwrankin.com
"Paul W. Rankin" <hello@paulwrankin.com> writes:
> On Wed, May 22 2019, Eli Zaretskii wrote:
>> Richard means the manual whjch the FSF prints and sells. If it's
>> too large, it will be more expensive.
>>
>> But there's a way to have that cake and eat it, too: we can have
>> certain portions of the manual conditioned by @ifnottex. We already
>> do that for some less important topics. So there's no need to argue
>> about this particular case.
>
> Makes sense. But getting immediate pushback just means I won't be
> contributing the topic.
In the given case, I believe it is not mandatory to document the whole
lisp-mnt package. It would suffice to document `lm-header' in the node
"(elisp) Library Headers".
Best regards, Michael.
next prev parent reply other threads:[~2019-05-22 7:49 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
2019-05-22 2:26 ` Eli Zaretskii
2019-05-22 2:49 ` Paul W. Rankin
2019-05-22 7:49 ` Michael Albinus [this message]
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=87ef4r6i9b.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hello@paulwrankin.com \
--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).