unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Bochannek <alex@bochannek.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 48801@debbugs.gnu.org
Subject: bug#48801: 28.0.50; [PATCH] Feature suggestion gnus-retrieve-headers check for nov-is-evil when agent is enabled
Date: Wed, 09 Jun 2021 11:47:32 -0700	[thread overview]
Message-ID: <m2zgvy7u4b.fsf@bochannek.com> (raw)
In-Reply-To: <83sg1qdhwj.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 09 Jun 2021 21:14:52 +0300")

[-- Attachment #1: Type: text/plain, Size: 631 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Alex Bochannek <alex@bochannek.com>
>> Date: Wed, 09 Jun 2021 11:05:14 -0700
>> Cc: 48801@debbugs.gnu.org
>> 
>> +One particular scenario in which it can be desirable to not use
>> +@samp{XOVER} is for @code{nnvirtual} groups in order to support
>> +limiting by extra headers (e.g., by the newsgroup of its component
>> +groups.) Because group parameters are not inherited, a separate select
>           ^^
> Our conventions are to leave 2 spaces between sentences.

Thanks for pointing that out! Is there a style document for code and
documentation that I could use as a reference?


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 760 bytes --]

diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi
index 32ba5aee92..e7ced97ef9 100644
--- a/doc/misc/gnus.texi
+++ b/doc/misc/gnus.texi
@@ -5246,6 +5246,13 @@ To From Newsgroups
 Be aware, though, that this will make entering an @acronym{NNTP} group
 much, much slower, so this is not recommended.
 
+One particular scenario in which it can be desirable to not use
+@samp{XOVER} is for @code{nnvirtual} groups in order to support
+limiting by extra headers (e.g., by the newsgroup of its component
+groups.)  Because group parameters are not inherited, a separate
+select method for the component groups with the appropriate
+@code{nov-is-evil} set as a method variable is required.
+
 
 @node Summary Buffer Mode Line
 @subsection Summary Buffer Mode Line

[-- Attachment #3: Type: text/plain, Size: 10 bytes --]

-- 
Alex.

  reply	other threads:[~2021-06-09 18:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 21:13 bug#48801: 28.0.50; [PATCH] Feature suggestion gnus-retrieve-headers check for nov-is-evil when agent is enabled Alex Bochannek
2021-06-03  7:59 ` Lars Ingebrigtsen
2021-06-03 18:01   ` Alex Bochannek
2021-06-04  9:35     ` Lars Ingebrigtsen
2021-06-04 17:40       ` Alex Bochannek
2021-06-06  9:36         ` Lars Ingebrigtsen
2021-06-06 17:51           ` Alex Bochannek
2021-06-08  9:57             ` Lars Ingebrigtsen
2021-06-08 15:50               ` Alex Bochannek
2021-06-09  5:35               ` Alex Bochannek
2021-06-09  9:59                 ` Lars Ingebrigtsen
2021-06-09 18:05                   ` Alex Bochannek
2021-06-09 18:14                     ` Eli Zaretskii
2021-06-09 18:47                       ` Alex Bochannek [this message]
2021-06-09 18:55                         ` Eli Zaretskii
2021-06-09 19:04                           ` Alex Bochannek
2021-06-12 12:10                         ` Lars Ingebrigtsen
2021-06-12 17:49                           ` Alex Bochannek

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=m2zgvy7u4b.fsf@bochannek.com \
    --to=alex@bochannek.com \
    --cc=48801@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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 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).