From: Jens Schmidt 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: 64154@debbugs.gnu.org
Subject: bug#64154: 29.0.92; Provide additional details on GnuPG and EPA usage in epa.texi
Date: Thu, 29 Jun 2023 23:10:41 +0200 [thread overview]
Message-ID: <056aa3cb-51e6-dc01-a299-1200ba79e211@vodafonemail.de> (raw)
In-Reply-To: <90275992-b539-e611-d92b-9bfe57d9d58d@vodafonemail.de>
On 2023-06-18 19:32, Eli Zaretskii wrote:
Back from greener pastures, sorry for the delay.
>> +@node GnuPG Pinentry
>> +@chapter GnuPG Pinentry
>
> Pleased add an index entry for the subject of this chapter. In
> general, it is a good idea to have an index entry for each
> chapter/section/subsection naming is main subject.
Problem here being that epa.texi has no concept index yet. Should I
create one from the existing chapters/sections/subsections in a separate
patch?
And the next question is: Does this ("new documentation of existing
features") qualify for Emacs 29?
Thanks
next prev parent reply other threads:[~2023-06-29 21:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dcb43cbb-61aa-417a-7da0-1b86223038ef@vodafonemail.de>
[not found] ` <83wn02r0s7.fsf@gnu.org>
2023-06-18 17:32 ` bug#64154: Fwd: Some additions to the EasyPG Assistant's manual Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-29 21:10 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-06-30 5:54 ` bug#64154: 29.0.92; Provide additional details on GnuPG and EPA usage in epa.texi Eli Zaretskii
2023-06-30 19:13 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-30 19:32 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-30 20:54 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-01 6:01 ` Eli Zaretskii
2023-07-01 11:13 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-01 11:57 ` Eli Zaretskii
2023-07-01 16:56 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-01 17:19 ` Eli Zaretskii
2023-07-01 17:56 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-01 18:49 ` Eli Zaretskii
2023-07-01 20:20 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-02 4:59 ` Eli Zaretskii
2023-07-02 7:13 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-02 8:18 ` Eli Zaretskii
2023-07-02 11:54 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-02 12:16 ` Eli Zaretskii
2023-07-02 11:55 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-02 12:18 ` Eli Zaretskii
2023-07-01 5:37 ` Eli Zaretskii
2023-07-02 2:15 ` Richard Stallman
2023-07-02 7:34 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-08 20:31 ` bug#64154: Some additions to the EasyPG Assistant's manual Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-09 7:24 ` Eli Zaretskii
2023-07-09 10:18 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-09 11:26 ` Eli Zaretskii
2023-07-09 14:41 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-11 11:02 ` Eli Zaretskii
2023-07-11 20:24 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-13 7:52 ` Eli Zaretskii
2023-07-13 18:46 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-18 17:29 bug#64154: 29.0.92; Provide additional details on GnuPG and EPA usage in epa.texi Jens Schmidt 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=056aa3cb-51e6-dc01-a299-1200ba79e211@vodafonemail.de \
--to=bug-gnu-emacs@gnu.org \
--cc=64154@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
/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).