From: "Martin Bähr" <mbaehr@email.archlab.tuwien.ac.at>
To: Matthieu Rakotojaona <matthieu.rakotojaona@gmail.com>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] use-mail branch and other work
Date: Tue, 01 Apr 2014 05:46:29 +0200 [thread overview]
Message-ID: <1396321899-sup-4786@email.archlab.tuwien.ac.at> (raw)
In-Reply-To: <1396294116-sup-6519@kpad>
Excerpts from Matthieu Rakotojaona's message of 2014-03-31 21:42:57 +0200:
> > add support for a "new" state that is different from unread.
> > the idea here is that the new state of a message can be cleared without
> > reading the message or marking it as read. this distinction is important
> > because i have lots of old unread mail, and so i can't see where i have
> > actual new mail.
> Isn't that more ore less achievable with the inbox label ? It is added
> automatically to new messages unless you explicitely specify otherwise.
the inbox is where all the important new mail comes in. it is easy to reach
with "I", which is important. i do not want mailing list emails in the inbox. i
have some very active lists, which would just flodd the inbox view and drown
out all other new messages.
i could use the inbox if i made a search that excludes all mailinglists, but
that search would take more than one keystroke to reach. and it would not give me other features, such as a count of new messages in the label-list
"new" is a state that should be automatically cleared when i read a message or
when the message/thread goes out of view.
i currently have it working semi-automaticly in
https://github.com/eMBee/sup/commit/9debc5be804f6dc38cc9d4a14d5eead0337b1e22
the new state is cleared when a thread is read or when i refresh with @
in the label-list-mode, labels are sorted by the time of the latest new
message, and each label has a count of how many new messages this label has:
new 429 messages, 260 unread, 429 new - 5:21am
Unread 614916 messages, 614916 unread, 260 new - 5:21am
Inbox 928373 messages, 562870 unread, 9 new - 5:18am
news 91638 messages, 55560 unread, 74 new - 5:03am
fish 4037 messages, 2447 unread, 5 new - 3:33am
Spam 18456 messages, 11190 unread, 43 new - 3:26am
git 55779 messages, 33819 unread, 100 new - 2:53am
Replied 77 messages, 0 unread, 0 new - 2:08am
sup 6401 messages, 3880 unread, 0 new - Mar 31
Attachment 14521 messages, 8804 unread, 8 new - Mar 31
debian 13541 messages, 8210 unread, 10 new - Mar 31
fedora 221 messages, 89 unread, 14 new - Mar 31
i can now easily see where there are new messages, how recent they are, and how many.
> > some ideas:
> > i'd like the ability to apply a label change to all messages that match a
> > given search, not just the ones loaded into the buffer.
> Semi-answer: bin/sup-tweak-labels is this, except it's supposed to be
> used from the command line. Moreover you must exit sup because the index
> can't be shared safely.
ah, thanks, yes, that should solve this problem mostly.
> I don't know how we could manage to reproduce the bin/sup-tweak-labels
> _inside_ sup efficiently, but I'm open to the discussion.
i'd be happy for it to not be efficient. just some fire-and-forget command that
silently chuggs away in the background.
> You do have interesting ideas. Welcome on board :)
thank you.
greetings, martin.
--
eKita - the online platform for your entire academic life
hackerspace beijing - http://qike.info
--
chief engineer eKita.co
pike programmer pike.lysator.liu.se caudium.net societyserver.org
BLUG secretary beijinglug.org
foresight developer foresightlinux.org realss.com
unix sysadmin
Martin Bähr working in china http://societyserver.org/mbaehr/
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
prev parent reply other threads:[~2014-04-01 3:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 9:51 Martin Bähr
2014-03-30 20:47 ` Steven Schmeiser
2014-03-31 12:02 ` Gaute Hope
2014-03-31 12:09 ` Gaute Hope
2014-04-01 4:13 ` Martin Bähr
2014-03-31 19:42 ` Matthieu Rakotojaona
2014-03-31 20:57 ` Gaute Hope
2014-04-01 3:55 ` Martin Bähr
2014-04-01 3:46 ` Martin Bähr [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=1396321899-sup-4786@email.archlab.tuwien.ac.at \
--to=mbaehr@email.archlab.tuwien.ac.at \
--cc=matthieu.rakotojaona@gmail.com \
--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