From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Any way to control which articles Gnus summary shows by default?
Date: Wed, 04 Apr 2018 16:33:44 +0200 [thread overview]
Message-ID: <87y3i3m46v.fsf@web.de> (raw)
In-Reply-To: <86o9izi177.fsf@zoho.com> (Emanuel Berg's message of "Wed, 04 Apr 2018 14:51:56 +0200")
Emanuel Berg <moasen@zoho.com> writes:
> > A hack would probably call `gnus-summary-limit'
>
> Are you sure? That one isn't documented, but the interface doesn't
> have an argument or so to imply one can process articles differently.
AFAICT most commands of kind "insert*articles" and "limit-to-*" are
implemented on top of it.
> Did you manage to solve this the "hack"/hook way?
No, I didn't try, I don't want to. I'm quite sure doing it in a way
that it "works" somehow is easy. Doing it right so that maintainers can
be sure it does the right thing under any circumstances is the hard
part. The Gnus sources are complicated, so it's better you know what
you are doing.
Michael.
next prev parent reply other threads:[~2018-04-04 14:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11583.1522744082.27995.help-gnu-emacs@gnu.org>
2018-04-03 23:17 ` Any way to control which articles Gnus summary shows by default? Emanuel Berg
2018-04-03 23:28 ` Emanuel Berg
2018-04-04 7:00 ` Michael Heerdegen
2018-04-04 7:30 ` Eric Abrahamsen
2018-04-04 10:59 ` Michael Heerdegen
2018-04-04 11:31 ` Eric Abrahamsen
2018-04-04 14:41 ` Michael Heerdegen
2018-04-04 14:46 ` Michael Heerdegen
2018-04-06 14:52 ` Michael Heerdegen
2018-04-06 15:22 ` Eric Abrahamsen
2018-04-06 17:53 ` Eric Abrahamsen
2018-04-06 18:06 ` Eric Abrahamsen
2018-04-07 9:26 ` Michael Heerdegen
2018-04-07 12:33 ` Michael Heerdegen
2018-04-07 9:23 ` Michael Heerdegen
2018-04-08 14:17 ` Michael Heerdegen
2018-04-08 15:03 ` Eric Abrahamsen
2018-04-08 15:46 ` Michael Heerdegen
2018-04-08 16:57 ` Eric Abrahamsen
2018-04-08 19:01 ` Eric Abrahamsen
2018-04-08 23:59 ` Eric Abrahamsen
2018-04-09 14:12 ` Michael Heerdegen
2018-04-09 16:36 ` Eric Abrahamsen
2018-04-09 19:59 ` Michael Heerdegen
2018-04-09 20:18 ` Eric Abrahamsen
2018-04-10 12:15 ` Michael Heerdegen
2018-04-10 16:27 ` Eric Abrahamsen
2018-04-10 20:12 ` Michael Heerdegen
2018-04-10 22:29 ` Eric Abrahamsen
2018-04-11 17:05 ` Michael Heerdegen
[not found] ` <mailman.11665.1522827199.27995.help-gnu-emacs@gnu.org>
2018-04-04 12:43 ` Emanuel Berg
2018-04-06 17:53 ` Eric Abrahamsen
2018-07-24 3:10 ` Robert Girault
[not found] ` <mailman.11664.1522825278.27995.help-gnu-emacs@gnu.org>
2018-04-04 12:51 ` Emanuel Berg
2018-04-04 14:33 ` Michael Heerdegen [this message]
[not found] ` <mailman.11689.1522852442.27995.help-gnu-emacs@gnu.org>
2018-04-04 14:48 ` Emanuel Berg
2018-04-03 8:27 Michael Heerdegen
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=87y3i3m46v.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@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.
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).