From: daniel@wagner-home.com (Daniel Wagner)
Subject: [sup-talk] Beginner questions
Date: Sun, 04 May 2008 18:02:49 -0700 [thread overview]
Message-ID: <1209949098-sup-4287@buckwheat> (raw)
In-Reply-To: <481E5936.7040600@gmail.com>
Excerpts from yanghatespam's message of Sun May 04 17:47:50 -0700 2008:
> If sup's thread-grouping is decent, then it would be neat/more accurate
> to extend sup somehow to instead use these groupings for the filtering.
> I.e., if an incoming message is grouped with a thread in which I was a
> participant, then leave it marked unread; otherwise, mark it read.
Well, sup already has a pretty nice (and similar) feature for killing
entire threads. The '&' key will archive a thread permanently; that is,
if new mails arrive in that thread, they will automatically be archived.
So, you can hit '&' once for each thread you don't want to read; the
rest will reappear in you inbox as new mails arrive in them.
It's a bit inverted from what you want, but maybe it will do? In any
case, if you want to extend sup, you should look at how that key works.
> (6) Scrolling through the buffer that is immediately presented to me
> when starting sup, I only see about 3 pages of threads. Is this
> correct? How do I get to the rest?
The 'M' key will load more threads.
Good luck!
~d
P.S. I'm running a slightly old version of sup, so the actual keys might
not be '&' and 'M' any more. '?' should list the available commands at
any time.
next prev parent reply other threads:[~2008-05-05 1:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 0:47 Yang Zhang
2008-05-05 1:02 ` Daniel Wagner [this message]
2008-05-05 2:08 ` Yang Zhang
2008-05-05 18:09 ` Marc Hartstein
2008-05-05 18:29 ` Yang Zhang
2008-05-19 23:38 ` William Morgan
2008-05-06 2:15 ` Christopher Warrington
2008-05-05 2:48 kendall at clarkparsia.com
2008-05-19 23:44 ` William Morgan
2008-08-03 23:17 Thorsten Kramer
2008-08-04 1:41 ` William Morgan
2008-08-05 21:52 ` Thorsten Kramer
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=1209949098-sup-4287@buckwheat \
--to=daniel@wagner-home.com \
/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