From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51648@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#51648: 28.0.60; `tab-bar-close-button' and `tab-bar-new-button' should be documented in the manual
Date: Sun, 07 Nov 2021 16:05:18 +0800 [thread overview]
Message-ID: <87tugov1a9.fsf@yahoo.com> (raw)
In-Reply-To: <83a6ig9zxc.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 07 Nov 2021 09:40:15 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Decisions about additions to the manual should not be taken too
> easily, because the manual is printed and sold by the FSF, and any
> addition to it makes the production of the manual more expensive.
This is a detail I didn't take into account when making my request,
thanks for pointing it out.
next prev parent reply other threads:[~2021-11-07 8:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878ry0y884.fsf.ref@yahoo.com>
2021-11-07 3:07 ` bug#51648: 28.0.60; `tab-bar-close-button' and `tab-bar-new-button' should be documented in the manual Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 7:12 ` Eli Zaretskii
2021-11-07 7:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 7:40 ` Eli Zaretskii
2021-11-07 8:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-11-07 17:37 ` Juri Linkov
2021-11-07 18:25 ` Eli Zaretskii
2021-11-07 18:31 ` Juri Linkov
2021-11-07 18:41 ` Eli Zaretskii
2021-11-07 20:00 ` Juri Linkov
2021-11-08 0:32 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-08 9:02 ` Juri Linkov
2022-09-15 16:20 ` Juri Linkov
2022-10-23 18:11 ` Juri Linkov
2021-11-08 17:46 ` Juri Linkov
2022-01-27 18:45 ` Juri Linkov
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=87tugov1a9.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=51648@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=luangruo@yahoo.com \
/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.