From: Matthias Vallentin <vallentin@icsi.berkeley.edu>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] (no subject)
Date: Sun, 14 Nov 2010 16:49:31 -0800 [thread overview]
Message-ID: <20101115004931.GD34938@icsi.berkeley.edu> (raw)
I am a Mutt user interested in switching to Sup. One thing that is not
clear to me is how to find new unread messages that skipped the inbox.
Coming from the world of mail folders, I can monitor each folder for
unread messages and switch to it when I see that a new one has arrived.
Often, a buffy tool (or the Mutt sidebar) can be used to display the
various folders with their new message counts. How would that mindset
translate to Sup? Would I have to regularly query all (or a just a
subset of) labels to get an idea whether label X "received" a new
message?
Matthias
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2010-11-15 1:34 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 0:49 Matthias Vallentin [this message]
2010-11-15 1:42 ` Edward Z. Yang
2010-11-15 6:57 ` Matthias Vallentin
2010-11-15 8:06 ` Helge Titlestad
2010-11-20 19:04 ` Matthias Vallentin
2010-11-21 1:10 ` Tero Tilus
2010-11-21 1:51 ` Matthias Vallentin
2010-11-15 1:46 ` Ben Walton
2010-11-15 1:50 ` Matias Aguirre
-- strict thread matches above, loose matches on Subject: below --
2011-12-10 3:08 Jason O'Conal
2009-06-08 0:02 Ben Walton
2009-06-11 23:50 ` Ben Walton
2009-06-12 3:44 ` William Morgan
2009-06-12 13:15 ` Ben Walton
2009-06-12 18:23 ` William Morgan
2009-06-01 1:01 Ben Walton
2009-06-01 1:04 ` Ben Walton
2009-06-01 2:13 ` Ben Walton
2009-06-04 2:04 ` Ross Macduff
2009-02-16 6:45 Michael John Stipicevic
2009-02-16 6:45 Michael John Stipicevic
2009-02-16 6:45 Michael John Stipicevic
2009-02-16 6:45 Michael John Stipicevic
2009-02-16 6:45 Michael John Stipicevic
2009-02-16 6:45 Michael John Stipicevic
2009-02-16 6:45 Michael John Stipicevic
2009-02-16 6:44 Michael John Stipicevic
2009-02-16 6:27 Michael John Stipicevic
2009-02-16 6:25 Michael John Stipicevic
2009-02-16 6:25 Michael John Stipicevic
2009-02-16 6:25 Michael John Stipicevic
2009-02-16 8:53 ` Ian Smith
2009-02-16 14:08 ` William Morgan
2009-02-16 14:42 ` Mike Stipicevic
2009-02-16 6:25 Michael John Stipicevic
2009-02-16 6:25 Michael John Stipicevic
2009-02-16 6:25 Michael John Stipicevic
2009-02-16 6:25 Michael John Stipicevic
2009-02-16 6:25 Michael John Stipicevic
2008-01-05 19:29 thefed
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=20101115004931.GD34938@icsi.berkeley.edu \
--to=vallentin@icsi.berkeley.edu \
--cc=sup-talk@rubyforge.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