From: Ted Zlatanov <tzz@lifelogs.com>
To: jidanni@jidanni.org
Cc: ding@gnus.org, rdc1x@comcast.net
Subject: Re: Idea: gnus-summary-next-thread-conclusion
Date: Fri, 31 Oct 2008 06:51:27 -0500 [thread overview]
Message-ID: <m2k5bphtj4.fsf@getconnected.com> (raw)
In-Reply-To: <87zlkl5lth.fsf@jidanni.org>
On Fri, 31 Oct 2008 14:18:50 +0800 jidanni@jidanni.org wrote:
j> Idea: there should be new commands:
j> gnus-summary-next-thread-conclusion
j> gnus-summary-prev-thread-conclusion
j> that jump to the "concluding article" of the next and previous
j> threads, so you can get to the bottom of the story right away.
j> They should also mark the whole thread as read by default, even if
j> (defcustom gnus-mark-article-hook '(gnus-summary-mark-read-and-unread-as-read)...
j> has been set to nil perhaps.
j> What the definition of the concluding article (deepest in the thread?,
j> newest?) is, I leave up to you all, or make a variable.
j> These functions are not something I hardly would use so often to
j> bother to write a personal function, but maybe others might find the
j> idea worthy to add to gnus.
Since both the definition of the function and its possible uses are
nebulous, I don't think it's needed in the Gnus core.
Ted
prev parent reply other threads:[~2008-10-31 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 6:18 jidanni
2008-10-31 11:51 ` Ted Zlatanov [this message]
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=m2k5bphtj4.fsf@getconnected.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=jidanni@jidanni.org \
--cc=rdc1x@comcast.net \
/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).