From: Michael Heerdegen <michael_heerdegen@web.de>
To: info-gnus-english@gnu.org
Subject: Re: Highlight process-marked files in Gnus summary?
Date: Mon, 26 Jul 2021 00:16:15 +0200 [thread overview]
Message-ID: <87fsw2m440.fsf@web.de> (raw)
In-Reply-To: <87fsw2upfu.fsf@gnu.org>
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).
You might also want to test something like
#+begin_src emacs-lisp
(defun my-gnus-limit-to-current-thread ()
(interactive)
(let ((a (gnus-summary-article-number)))
(gnus-summary-limit
(gnus-summary-articles-in-thread
(let ((a a))
(dotimes (_ (gnus-summary-thread-level))
(cl-callf gnus-summary-article-parent a))
a)))
(gnus-summary-goto-subject a)))
#+end_src
Michael.
_______________________________________________
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-25 22:16 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 [this message]
2021-07-26 2:26 ` Roland Winkler
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=87fsw2m440.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=info-gnus-english@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 NNTP newsgroup(s).