From: grant@antiflux.org (Grant Hollingworth)
Subject: [sup-talk] [PATCH] label-list-mode with no unread messages
Date: Wed, 21 Nov 2007 12:53:34 -0700 [thread overview]
Message-ID: <1195673904-sup-7215@spooky> (raw)
This patch sets the status to "No labels with unread messages" for label-list-mode when unread_only is toggled on and there are, well, no labels with unread messages. I thought the blank buffer looked a little odd.
It would be nicer if label-list-mode wasn't modal. I keep hitting 'b' and 'x' and 'q' with no effect, and then hitting C-g. It would be more work to keep the counts up to date, but that could use some work anyway. If I read all the new mail in one label and then activate label-list-mode, the unread count will be wrong... unless I kill the label buffer or sync it first.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: label-list-no-unread.diff
Type: application/octet-stream
Size: 912 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071121/760d8bb6/attachment.obj
next reply other threads:[~2007-11-21 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 19:53 Grant Hollingworth [this message]
2007-11-24 20:47 ` William Morgan
2007-11-26 18:57 ` Grant Hollingworth
2007-12-10 2:51 ` 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=1195673904-sup-7215@spooky \
--to=grant@antiflux.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