Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Andrew Cohen <cohen@bu.edu>
To: info-gnus-english@gnu.org
Subject: Re: Finding last messages in a thread
Date: Fri, 01 May 2020 10:12:43 +0800	[thread overview]
Message-ID: <87v9lgv1wk.fsf@ust.hk> (raw)
In-Reply-To: <87lfmcwik8.fsf@web.de>


>>>>> "MH" == Michael Heerdegen <michael_heerdegen@web.de> writes:


[...]

    MH> But I have some questions first (somewhat interdependent):

    MH> (1) I wasn't able to discover this.  Should there be a menu
    MH> entry for this function?

Sure.

    MH> (2) It currently has the binding / T.  But it doesn't seem to be
    MH> a pure limit command, since it also shows additional articles.
    MH> Do we want it like this?

    MH> (3) Will people call this more often with prefix arg?  If yes,
    MH> should we toggle the meaning of the prefix, or split the command
    MH> into two separate commands?

This part of gnus is a (slight) mess. There are commands for limiting
that are of the form 'gnus-summary-limit-to-x which indeed limit the
summary buffer given some criteria. Then there are several commands of
the form 'gnus-summary-limit-include-x whose purpose is to ADD to the
currently limited display some things that were hidden (dormant,
expunged, etc). That is what 'gnus-summary-limit-include-threads is for
(since often articles in the thread are hidden in the summary display;
for example you might have ticked articles and unticked articles in a
thread and the unticked articles are hidden).

Clearly limiting to and displaying hidden articles are independent, so
there are four possible outcomes for limiting and displaying based on
criterion "X". Ideally all of this would be cleaned up with a common
syntax for these functions. This would take a bit of work, and I'm not
sure its worth just changing things for the one case of threads. But if
anyone is eager to tackle this it would help clean up the code
significantly, and shouldn't be too much work.

Having said that, if you wanted to skip the work of cleaning everything
up I would favor creating a separate command for
'gnus-summary-limit-to-thread and remove the prefix-arg and the
associated code path from 'gnus-summary-limit-include-thread and change
the bindings (and the one use case in 'gnus-summary-refer-thread).

Best,
Andy






_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2020-05-01  2:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30  3:15 Michael Heerdegen
2020-04-30  4:16 ` Eric Abrahamsen
2020-04-30  4:46   ` Michael Heerdegen
2020-04-30  5:29     ` Eric Abrahamsen
2020-04-30  5:31 ` Lars Ingebrigtsen
2020-04-30  7:01   ` Andrew Cohen
2020-04-30  8:25     ` Andrew Cohen
2020-04-30 22:18       ` Michael Heerdegen
2020-05-01  0:27         ` Andrew Cohen
2020-05-01  1:27           ` Michael Heerdegen
2020-05-01  2:12             ` Andrew Cohen [this message]
2020-04-30 20:36 ` Achilles Yuce
2020-04-30 20:45   ` Michael Heerdegen
2020-04-30 20:52     ` Achilles Yuce

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=87v9lgv1wk.fsf@ust.hk \
    --to=cohen@bu.edu \
    --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).