Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: pierre@baillet.name (Pierre Baillet)
Subject: [sup-talk] [BUG] Killed thread and unread count
Date: Thu, 8 Nov 2007 11:22:29 +0100	[thread overview]
Message-ID: <6205b42d0711080222i119831cdl64edf4a3291a3078@mail.gmail.com> (raw)

Hi,

When an unread thread is killed, it is still marked as belonging to +inbox
and hence is accounted as unread by sup in the "Label list". However, when
displaying the +inbox labelled emails, this thread does not appear. I think
this behaviour may confuse the user. Shouldn't killed threads be marked as
read ?

-- 
Pierre Baillet <pierre at baillet.name>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/sup-talk/attachments/20071108/cbc7065b/attachment.html 


             reply	other threads:[~2007-11-08 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 10:22 Pierre Baillet [this message]
2007-11-11 23:57 ` William Morgan

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=6205b42d0711080222i119831cdl64edf4a3291a3078@mail.gmail.com \
    --to=pierre@baillet.name \
    /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