From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#64154: 29.0.92; Provide additional details on GnuPG and EPA usage in epa.texi Date: Sat, 01 Jul 2023 21:49:11 +0300 Message-ID: <83jzvjpivs.fsf@gnu.org> References: <83wn02r0s7.fsf@gnu.org> <90275992-b539-e611-d92b-9bfe57d9d58d@vodafonemail.de> <056aa3cb-51e6-dc01-a299-1200ba79e211@vodafonemail.de> <831qhtts01.fsf@gnu.org> <9e4c56f2-0124-fdf1-c719-ca6219c1ab28@vodafonemail.de> <3036a576-9260-8932-cb07-3941046f2dd8@vodafonemail.de> <83a5wgrwzj.fsf@gnu.org> <196f75be-0935-c481-8a9e-7157f3e650d0@vodafonemail.de> <83o7kvpn22.fsf@gnu.org> <7f41744d-bb32-1b0d-8fea-69f91b413b0c@vodafonemail.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7469"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 64154@debbugs.gnu.org To: Jens Schmidt Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jul 01 20:50:10 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qFffd-0001jX-EO for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 01 Jul 2023 20:50:09 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qFffY-0005Gg-EU; Sat, 01 Jul 2023 14:50:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qFffW-0005GT-W5 for bug-gnu-emacs@gnu.org; Sat, 01 Jul 2023 14:50:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qFffW-0004mn-NA for bug-gnu-emacs@gnu.org; Sat, 01 Jul 2023 14:50:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qFffW-0002Lg-JZ for bug-gnu-emacs@gnu.org; Sat, 01 Jul 2023 14:50:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 01 Jul 2023 18:50:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 64154 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 64154-submit@debbugs.gnu.org id=B64154.16882373448954 (code B ref 64154); Sat, 01 Jul 2023 18:50:02 +0000 Original-Received: (at 64154) by debbugs.gnu.org; 1 Jul 2023 18:49:04 +0000 Original-Received: from localhost ([127.0.0.1]:58697 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qFfeZ-0002KL-NW for submit@debbugs.gnu.org; Sat, 01 Jul 2023 14:49:04 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:33862) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qFfeX-0002Jr-AD for 64154@debbugs.gnu.org; Sat, 01 Jul 2023 14:49:02 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qFfeR-0004fh-8p; Sat, 01 Jul 2023 14:48:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=7rmO0x3yin1WiXO4IPsx+qOlQNhE34i/A0F7ufp/6FQ=; b=ZeMjne4nO7v6 kYYlQYwsQrDDwlppg8DdkW1I1vVznpnMwzdd7OY618oXOEu3WXqIKTFNXHY4Svvtp7G9Rm9+fHITj 4nyBZ52TclW0f655Z5lUscvtBABR25+8TflmeQwudeVZZ+35Isvrt+HlLx7JOAVQwy27pK8K+/mo8 jRn9Qh/OntkSeK5ZqYNZAa7MPbxv8GfNT95dsRezf9hFjEiK5kLL4s7rqEtDKd7HuJVur7JSDicqw pSBl64T2rkZ/AHDcZVRJxVSd9OHi3hld4jSzYFFM7HMSPGxzEslpo1omh0+dSwn7zz7h6NTgznBP3 vGCvvhJqcMLWgIAN6Yl/rw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qFfe9-0004iZ-Oa; Sat, 01 Jul 2023 14:48:55 -0400 In-Reply-To: <7f41744d-bb32-1b0d-8fea-69f91b413b0c@vodafonemail.de> (message from Jens Schmidt on Sat, 1 Jul 2023 19:56:08 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:264420 Archived-At: > Date: Sat, 1 Jul 2023 19:56:08 +0200 > Cc: 64154@debbugs.gnu.org > From: Jens Schmidt > > @cindex GnuPG version compatibility > @cindex version compatibility with GnuPG > @cindex compatibility with GnuPG > > so I hope we're closing in. > > Not sure though: Are these three entries "too redundant" in your > opinion? And if so, why would that hurt? They are not redundant, since they all start differently. But I would suggest to consider the first one for removal. > >> Similar problems arise if anybody actually cares looking at the > >> alphabetically ordered index, be it in an online reader or in > >> print. (After all an index should be there for alphabetical > >> lookup, shouldn't it?) > > > > Not in the on-line manual, no. Index entries in Info are intended to > > be used without going to the Index node at all. > > What about those who use pdf or even print this stuff? The alphabetic order of the index in the printed versions exists to help finding the index entries. People still first think about what they want to find, and only then look it up. > >> Finally, I noticed that the index entries are not quite consistent > >> w.r.t. tense: Some use present tense, some present continuous. I > >> could change that ... > > > > There are no rules here, only common sense and the projected use by > > the readers. > > Does this "no rules" relate to only to my last statement or to index > entries in general? The former. > Because in general you seem to have quite a bunch of rules, and > well-founded ones, and if had known these before we could have saved > a round-trip or two. But I don't even dare to propose changing the > Texinfo manual ... The Texinfo manual doesn't need to be changed. It's a very good manual. As for "no rules", the most important rule for index entries is that they should fit what people have in mind when they look for the subject. All the rest are corollaries and gray hair gained by experience.