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 09:00:57 +0200 [thread overview]
Message-ID: <87vad78nh2.fsf@web.de> (raw)
In-Reply-To: <86lge3ric2.fsf@zoho.com> (Emanuel Berg's message of "Wed, 04 Apr 2018 01:17:01 +0200")
Emanuel Berg <moasen@zoho.com> writes:
> Interesting but, isn't this exactly what happens when you tick an
> article? So is there some side-effect that is undesired for this
> purpose or why don't you want to use it?
I still try to find a good workflow for my Inbox. In the past, I used
to tick nearly all articles, or make them unread, just to make them
appear the next time I select the group.
What I want in general is more control: I want to decide myself how Gnus
decides which articles it presents to me when I select a group. In
particular, I want to have it depend on the information present in the
registry.
> What do you mean by "set" article?
I wrote "set unread" or so and meant "make the article unread".
> BTW `M M i' is undefined for me so maybe it is a new feature in Emacs
> 25 or did you configure that?
It's a feature when you enable the Gnus registry:
(info "(gnus) Store custom flags and keywords")
Seems not many people use it so far, though.
> If you indeed got it to work, how about adding it to some hook/advice
> each time you enter a group?
I think you shouldn't need a hack to do this kind of thing. A hack
would probably call `gnus-summary-limit', but it would be better if it
would be configurable out of the box. Which I think is not the case.
The code responsible for group selection is quite complex, but I have
the impression that these things are hardcoded.
Thanks,
Michael.
next prev parent reply other threads:[~2018-04-04 7:00 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 [this message]
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
[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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vad78nh2.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.
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.