From: "Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 67469@debbugs.gnu.org
Subject: bug#67469: [PATCH] Fix typo in Gnus manual
Date: Mon, 27 Nov 2023 00:27:25 +0100 [thread overview]
Message-ID: <m1y1ekayea.fsf@yahoo.es> (raw)
In-Reply-To: m1y1ekayea.fsf.ref@yahoo.es
[-- Attachment #1: Type: text/plain, Size: 74 bytes --]
Tags: patch
This patch fixes a small typo in the Gnus manual. Thanks.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Fix-typo-in-Gnus-manual.patch --]
[-- Type: text/patch, Size: 1050 bytes --]
From 2086c33e34f85ed959160568ad0eb44bc7480a96 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Mart=C3=ADn?= <dmartin@Daniels-MacBook-Pro.local>
Date: Mon, 27 Nov 2023 00:22:20 +0100
Subject: [PATCH] ;; Fix typo in Gnus manual
---
doc/misc/gnus.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi
index 582038d973f..586e4b94ba1 100644
--- a/doc/misc/gnus.texi
+++ b/doc/misc/gnus.texi
@@ -21596,7 +21596,7 @@ Searching
Search queries can be specified one of two ways: either using the
syntax of the engine responsible for the group you're searching, or
using Gnus' generalized search syntax. Set the option
-@code{gnus-search-use-parsed-queries} to a non-@code{nil} value to used the
+@code{gnus-search-use-parsed-queries} to a non-@code{nil} value to use the
generalized syntax. The advantage of this syntax is that, if you have
multiple backends indexed by different engines, you don't need to
remember which one you're searching---it's also possible to issue the
--
2.42.0
next parent reply other threads:[~2023-11-26 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1y1ekayea.fsf.ref@yahoo.es>
2023-11-26 23:27 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-11-27 12:19 ` bug#67469: [PATCH] Fix typo in Gnus manual Eli Zaretskii
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=m1y1ekayea.fsf@yahoo.es \
--to=bug-gnu-emacs@gnu.org \
--cc=67469@debbugs.gnu.org \
--cc=mardani29@yahoo.es \
/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).