From: Ico Doornekamp <sup@zevv.nl>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Recognizing new mails.
Date: Sun, 23 Mar 2014 20:57:31 +0100 [thread overview]
Message-ID: <1395604436-sup-3844@pruts.nl> (raw)
In-Reply-To: <1395598271-sup-6267@kpad>
Sorry for the noise, I caused this problem myself: I use some mail
filtering using procmail to set the 'X-Mark-As-Read: yes' flag for bulk
mail (mailing lists etc) so these do not trigger my you-have-new-mail
bells and whistles. I was kind of confused about the difference between
'new' and 'unread' mail, thus messing up sup's behaviour.
* On 2014-03-23 19:25:00 +0100, Matthieu Rakotojaona wrote:
> Excerpts from Ico's message of 2014-03-23 14:15:51 +0100:
> > Does sup track read/unread for individual mails? For example, I open a
> > thread with 3 mails and read them all. The thread drops from my inbox.
> >
> > A few hours later I find the thread back in my inbox and open it again,
> > it now has 6 mails. How do I know which 3 are the new ones? Only the
> > last one is opened by default, but how do I tell which others I still
> > need to read?
> >
> > Is there a way to have unread mails unfolded by default?
>
> Weird, on my sup I have all new mails unfolded by default, and the focus
> is on the first one that is unfolded (either because it's unread or
> starred). That state is kept separately for each message indeed, so in
> your scenario it behaves as you expect. What version are you running ?
>
> You can see which message is unread with the 'N' on each message's top
> line.
>
--
:wq
^X^Cy^K^X^C^C^C^C
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2014-03-23 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 13:15 Ico
2014-03-23 18:25 ` Matthieu Rakotojaona
2014-03-23 19:57 ` Ico Doornekamp [this message]
2014-03-23 18:34 ` Gaute Hope
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=1395604436-sup-3844@pruts.nl \
--to=sup@zevv.nl \
--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