From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Richard Stallman <rms@gnu.org>
Cc: 66928@debbugs.gnu.org, jb@jeremybryant.net
Subject: bug#66928: [PATCH 2/2] Update names to match the docstring
Date: Mon, 13 Nov 2023 15:58:30 +0200 [thread overview]
Message-ID: <83ttppu54p.fsf@gnu.org> (raw)
In-Reply-To: <jwvedguu1w8.fsf-monnier+emacs@gnu.org> (bug-gnu-emacs@gnu.org)
> Cc: 66928@debbugs.gnu.org
> Date: Sun, 12 Nov 2023 16:02:00 -0500
> From: Stefan Monnier via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> > Are there any conventions for manual additions?
> > in particular to keep the number of printed pages limited is there a way
> > to say 'don't print this node'?
>
> I think there were ways to keep some parts out of the printed manual,
Yes, use @ifnottex..@end ifnottex.
> but I'm not sure this is relevant to the ELisp manual any more: is it
> still printed?
>
> The FSF shop still carries the Emacs manual and the ELisp intro, but
> I can't see the ELisp manual in there.
Richard?
next prev parent reply other threads:[~2023-11-13 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 12:49 bug#66928: [PATCH 2/2] Update names to match the docstring Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04 13:00 ` Eli Zaretskii
2023-11-04 16:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-04 22:56 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-05 14:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-06 22:55 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-12 21:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-13 13:58 ` Eli Zaretskii [this message]
2023-11-04 23:34 ` Jeremy Bryant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-12 20:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83ttppu54p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66928@debbugs.gnu.org \
--cc=jb@jeremybryant.net \
--cc=monnier@iro.umontreal.ca \
--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).