From: Anthony Martinez <pi+sup@pihost.us>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [PATCH 2/3] undoing read_and_archive should preserve unread state
Date: Sun, 3 Jan 2010 23:06:35 -0700 [thread overview]
Message-ID: <1262585196-25964-2-git-send-email-pi+sup@pihost.us> (raw)
In-Reply-To: <1262585196-25964-1-git-send-email-pi+sup@pihost.us>
---
lib/sup/modes/inbox-mode.rb | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/lib/sup/modes/inbox-mode.rb b/lib/sup/modes/inbox-mode.rb
index ad3a864..852ddb7 100644
--- a/lib/sup/modes/inbox-mode.rb
+++ b/lib/sup/modes/inbox-mode.rb
@@ -66,9 +66,10 @@ class InboxMode < ThreadIndexMode
return unless cursor_thread
thread = cursor_thread # to make sure lambda only knows about 'old' cursor_thread
+ was_unread = thread.labels.member? :unread
UndoManager.register "reading and archiving thread" do
thread.apply_label :inbox
- thread.apply_label :unread
+ thread.apply_label :unread if was_unread
add_or_unhide thread.first
end
--
1.6.5
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-01-04 6:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 6:06 [sup-devel] [PATCH 1/3] punctuate "No new messages." consistently between poll, jump_to_next_new Anthony Martinez
2010-01-04 6:06 ` Anthony Martinez [this message]
2010-01-04 6:06 ` [sup-devel] [PATCH 3/3] make the undo hooks also save the threads Anthony Martinez
2010-01-05 21:26 ` William Morgan
2010-01-05 22:45 ` [sup-devel] [PATCH-insta-save] " Anthony Martinez
2010-01-05 22:45 ` [sup-devel] [PATCH] " Anthony Martinez
2010-01-05 23:47 ` [sup-devel] [PATCH-insta-save] " William Morgan
2010-01-05 21:25 ` [sup-devel] [PATCH 2/3] undoing read_and_archive should preserve unread state William Morgan
2010-01-05 21:25 ` [sup-devel] [PATCH 1/3] punctuate "No new messages." consistently between poll, jump_to_next_new 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=1262585196-25964-2-git-send-email-pi+sup@pihost.us \
--to=pi+sup@pihost.us \
--cc=sup-devel@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