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: Sat, 1 Jul 2023 22:20:12 +0200 [thread overview]
Message-ID: <5fd3e9fe-4676-99dd-0931-992f71be8728@vodafonemail.de> (raw)
In-Reply-To: <83jzvjpivs.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
On 2023-07-01 20:49, Eli Zaretskii wrote:
Attached a third patch - please review 2nd and 3rd combined against 1st.
>> @cindex GnuPG version compatibility
>> @cindex version compatibility with GnuPG
>> @cindex compatibility with GnuPG
>
> They are not redundant, since they all start differently. But I would
> suggest to consider the first one for removal.
Why, then? I can imagine using that as index search, for example if I
remember that the section is named like that. Plus it does not seem to
break completion.
> The Texinfo manual doesn't need to be changed. It's a very good
> manual. [...]
At least w.r.t. to capitalization you both seem to fundamentally
disagree (quotes from "Index Entries(texinfo)"):
[...] capitalizing only proper
names and acronyms that always call for uppercase letters.
This is the case convention we use in most GNU manuals'
indices.
OTOH here you completely agree:
Like typesetting, the construction of an index is a skilled
art, the subtleties of which may not be appreciated until you
need to do it yourself.
[-- Attachment #2: 0003-Brush-up-index-entries-after-review.patch --]
[-- Type: text/x-patch, Size: 4925 bytes --]
From 8335d96553e2d29df0bffceaef9022c38beab1ff Mon Sep 17 00:00:00 2001
From: Jens Schmidt <jschmidt4gnu@vodafonemail.de>
Date: Sat, 1 Jul 2023 21:53:31 +0200
Subject: [PATCH] Brush up index entries after review
* doc/misc/epa.texi (Top, Overview, Key management)
(Cryptographic operations on regions, Cryptographic operations on files)
(Encrypting/decrypting gpg files, Querying a key server): Brush up
index entries after review. (Bug#64154)
---
doc/misc/epa.texi | 38 +++++++++++++++++++-------------------
1 file changed, 19 insertions(+), 19 deletions(-)
diff --git a/doc/misc/epa.texi b/doc/misc/epa.texi
index 4b998939ef5..edfe37de816 100644
--- a/doc/misc/epa.texi
+++ b/doc/misc/epa.texi
@@ -44,9 +44,9 @@
@node Top
@top EasyPG Assistant User's Manual
-@cindex EasyPG Assistant
-@cindex GNU Privacy Guard
-@cindex GnuPG
+@cindex easypg assistant
+@cindex gnu privacy guard
+@cindex gnupg
EasyPG Assistant is an Emacs user interface to GNU Privacy Guard
(GnuPG, @pxref{Top, , Top, gnupg, Using the GNU Privacy Guard}).
@@ -81,7 +81,7 @@ Top
@node Overview
@chapter Overview
-@cindex features of EasyPG Assistant
+@cindex features of easypg assistant
EasyPG Assistant provides the following features.
@@ -96,7 +96,7 @@ Overview
@node Quick start
@chapter Quick Start
-@cindex introduction to EasyPG Assistant
+@cindex introduction to easypg assistant
EasyPG Assistant commands are prefixed by @samp{epa-}. For example,
@@ -134,7 +134,7 @@ Key management
@cindex key management
@cindex key ring, browsing
-@cindex browse the key ring
+@cindex browse key ring
Probably the first step of using EasyPG Assistant is to browse your
keyring. @kbd{M-x epa-list-keys} is corresponding to @samp{gpg
--list-keys} from the command line.
@@ -223,9 +223,9 @@ Key management
@node Cryptographic operations on regions
@section Cryptographic Operations on Regions
@cindex cryptographic operations on regions
-@cindex region operations
+@cindex region operations, cryptographic
-@cindex decrypt a region
+@cindex decrypt region
@deffn Command epa-decrypt-region start end
Decrypt the current region between @var{start} and @var{end}. It
replaces the region with the decrypted text.
@@ -239,7 +239,7 @@ Cryptographic operations on regions
command does not alter the original text around armors.
@end deffn
-@cindex verify a region
+@cindex verify region
@deffn Command epa-verify-region start end
Verify the current region between @var{start} and @var{end}. It sends
the verification result to the minibuffer or a popup window. It
@@ -255,7 +255,7 @@ Cryptographic operations on regions
not alter the original text around OpenPGP cleartext blocks.
@end deffn
-@cindex sign a region
+@cindex sign region
@deffn Command epa-sign-region start end signers type
Sign the current region between @var{start} and @var{end}. By
default, it creates a cleartext signature. If a prefix argument is
@@ -263,7 +263,7 @@ Cryptographic operations on regions
type.
@end deffn
-@cindex encrypt a region
+@cindex encrypt region
@deffn Command epa-encrypt-region start end recipients sign signers
Encrypt the current region between @var{start} and @var{end}. It will
let you select recipients. If a prefix argument is given, it will
@@ -276,24 +276,24 @@ Cryptographic operations on files
@cindex cryptographic operations on files
@cindex file operations, cryptographic
-@cindex decrypt a file
+@cindex decrypt file
@deffn Command epa-decrypt-file file &optional output
Decrypt @var{file}. If you do not specify the name @var{output} to
use for the decrypted file, this function prompts for the value to use.
@end deffn
-@cindex verify a file
+@cindex verify file
@deffn Command epa-verify-file file
Verify @var{file}.
@end deffn
-@cindex sign a file
+@cindex sign file
@deffn Command epa-sign-file file signers type
Sign @var{file}. If a prefix argument is given, it will let you
select signing keys, and then a signature type.
@end deffn
-@cindex encrypt a file
+@cindex encrypt file
@deffn Command epa-encrypt-file file recipients
Encrypt @var{file}. It will let you select recipients.
@end deffn
@@ -487,7 +487,7 @@ Encrypting/decrypting gpg files
@node Querying a key server
@section Querying a Key Server
-@cindex query a key server
+@cindex query key server
@cindex key server, querying
The @code{epa-search-keys} command can be used to query a
@@ -503,9 +503,9 @@ Querying a key server
@node GnuPG version compatibility
@chapter GnuPG Version Compatibility
-@cindex GnuPG version compatibility
-@cindex version compatibility with GnuPG
-@cindex compatibility with GnuPG
+@cindex gnupg version compatibility
+@cindex version compatibility with gnupg
+@cindex compatibility with gnupg
As of February 2016, there are three active branches of GnuPG: 2.1,
2.0, and 1.4. All those branches should work flawlessly with Emacs
--
2.30.2
next prev parent reply other threads:[~2023-07-01 20:20 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 ` 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
2023-06-30 5:54 ` 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 [this message]
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=5fd3e9fe-4676-99dd-0931-992f71be8728@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).