From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] the num_inbox_unread variable
Date: Sat, 16 Feb 2008 12:09:28 -0800 [thread overview]
Message-ID: <1203192425-sup-1910@south> (raw)
In-Reply-To: <1202508462-sup-2051@clarabella.clarabella>
Reformatted excerpts from Giorgio Lando's message of 2008-02-08:
> I have a small problem with the num_inbox_unread variable, which is
> used for example in the status-bar-text.rb: in the number of unread
> messages the messages belonging to killed threads are included, but,
> from the name of the variable, I do not think that this is the
> expected behaviour (they are unread, but they are not the inbox.
Yes, this is a known bug. Killed threads need a little more work.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-02-16 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 22:10 Giorgio Lando
2008-02-16 20:09 ` William Morgan [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=1203192425-sup-1910@south \
--to=wmorgan-sup@masanjin.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