all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bake Timmons <65pandas@gmail.com>
To: 25275@debbugs.gnu.org
Subject: bug#25275: Fix `mail-sources' value of `(group)' in Gnus manual
Date: Mon, 26 Dec 2016 00:00:15 -0500	[thread overview]
Message-ID: <87o9zze140.fsf@speedymail.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: 0001-Fix-mail-sources-value-of-group-in-Gnus-manual.patch --]
[-- Type: text/x-patch, Size: 1085 bytes --]

From 4be32e5a0e3476f61d111c8a66546fa8b63c0f9c Mon Sep 17 00:00:00 2001
From: Bake Timmons <b2timmons@speedymail.org>
Date: Sun, 25 Dec 2016 23:42:52 -0500
Subject: [PATCH] Fix `mail-sources' value of `(group)' in Gnus manual

* doc/misc/gnus.texi (Mail Source Specifiers):
Replace wrong `mail-sources' value of `(group)' in Gnus manual with
the correct `((group))' value.
---
 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 c34dd7caf0..393787c33a 100644
--- a/doc/misc/gnus.texi
+++ b/doc/misc/gnus.texi
@@ -14656,7 +14656,7 @@ an additional mail source for a particular group by including the
 @code{group} mail specifier in @code{mail-sources}, and setting a
 @code{mail-source} group parameter (@pxref{Group Parameters}) specifying
 a single mail source.  When this is used, @code{mail-sources} is
-typically just @code{(group)}; the @code{mail-source} parameter for a
+typically just @code{((group))}; the @code{mail-source} parameter for a
 group might look like this:
 
 @lisp
-- 
2.11.0






             reply	other threads:[~2016-12-26  5:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-26  5:00 Bake Timmons [this message]
2016-12-27  6:39 ` bug#25275: Fix `mail-sources' value of `(group)' in Gnus manual Katsumi Yamaoka

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=87o9zze140.fsf@speedymail.org \
    --to=65pandas@gmail.com \
    --cc=25275@debbugs.gnu.org \
    /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.