From: Roland Winkler <winkler@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: info-gnus-english@gnu.org
Subject: Re: Highlight process-marked files in Gnus summary?
Date: Sun, 25 Jul 2021 21:26:36 -0500 [thread overview]
Message-ID: <87y29tu7xf.fsf@gnu.org> (raw)
In-Reply-To: <87fsw2m440.fsf@web.de> (Michael Heerdegen's message of "Mon, 26 Jul 2021 00:16:15 +0200")
On Mon, Jul 26 2021, Michael Heerdegen wrote:
> Roland Winkler <winkler@gnu.org> writes:
>
>> I found this old thread. Could it make sense to have a minor mode
>> that puts the `invisible' text property on all lines without
>> process-mark?
>
> I played with limiting since then (a concept that is a bit more advanced
> than making lines invisible and already exists).
>
> AFAIK there is no command that lets you limit to process marked
> articles, but it should be trivial to write using `gnus-summary-limit'
> (limits to a given article list).
Yes, thank you, limiting goes very much in the direction I want.
-- I like the two-step process of first marking the messages I want, and
only afterwards limiting the summary buffer because I can check whether
I have identified all messages I wanted to identify before the unmarked
messages become invisible.
Hopefully, it will be not too difficult to teach Gnus to limit the
Summary buffer based on the process-mark.
> You might also want to test something like
>
> #+begin_src emacs-lisp
> (defun my-gnus-limit-to-current-thread ()
Thanks! - If gnus can identify a thread correctly, the problem is pretty
much solved anyway. I am concerned about the annoying cases where the
discussion of a topic spreads out into multiple threads because someone
continued the discussion with a new message using a different subject
header and ignoring the references headers used previously. Typically,
this takes me multiple iterations of hand-crafted search criteria to
identify all messages that have contributed to the discussion of a
topic.
It just came to my mind: does Gnus allow one to add a custom header like
a "topic ID" that could help me two months later when I need to revisit
the discussion of a topic that was distributed over multiple apparently
unrelated threads?
There are all kinds of Gnus commands for article washing and
manipulating article headers. Yet I have not identified anything that
could be (mis-) used for such a purpose.
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2021-07-26 2:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 2:42 Michael Heerdegen
2020-05-18 15:38 ` Eric Abrahamsen
2020-05-19 13:47 ` Lars Ingebrigtsen
2020-05-19 23:13 ` Michael Heerdegen
2020-05-22 13:00 ` Lars Ingebrigtsen
2021-07-25 20:08 ` Roland Winkler
2021-07-25 22:16 ` Michael Heerdegen
2021-07-26 2:26 ` Roland Winkler [this message]
2021-07-27 0:47 ` Michael Heerdegen
2021-07-25 22:20 ` Eric Abrahamsen
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=87y29tu7xf.fsf@gnu.org \
--to=winkler@gnu.org \
--cc=info-gnus-english@gnu.org \
--cc=michael_heerdegen@web.de \
/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 NNTP newsgroup(s).