From: "Martin Bähr" <mbaehr@email.archlab.tuwien.ac.at>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] use-mail branch and other work
Date: Tue, 01 Apr 2014 06:13:44 +0200 [thread overview]
Message-ID: <1396324522-sup-8837@email.archlab.tuwien.ac.at> (raw)
In-Reply-To: <1396267373-sup-7639@qwerzila>
Excerpts from Gaute Hope's message of 2014-03-31 14:09:56 +0200:
> > add support for a "new" state that is different from unread.
> Perhaps you followed the discussion with Ico / Zevv on irc? There might
> be a solution together with the proposed hooks in #276, or are you
> looking for something more integrated?
new state operates on the thread-index.
a message is new if it has not been seen in an index.
if i have read the cubject-line and decided that i don't want to read this
thread, then at that point it is no longer new. (of course if i do read it, it
is also no longer new)
i have this mostly working in
https://github.com/eMBee/sup/commit/9debc5be804f6dc38cc9d4a14d5eead0337b1e22
since we don't have a ruby mind-reader gem, i am currently using @ refresh to
clear the new state. other options could be to detect when the cursor is
scrolled over a message, or when the buffer is closed or hidden when i switch
to another buffer.
initially i cleared the new state when the thread-index was loaded, but that
meant i could not see what was actually new, so i switched it to refresh.
> Some of these might be harder to do with sup since we don't keep an
> adress book.
for another idea that i have in mind, this is something i'd like to change.
> > i'd like to treat saved searches as virtual folders. they should be in a
> > combined list with labels, and i'd like to be able to open them by typing the
> > name in the search prompt.
>
> You can presse enter after searching to get a list, but I agree, it
> could be a streamlined way to do these things.
that's what i do now, i hardwired \+enter as the key-sequence to get the list.
but it means i have to deal with two lists, which is not wrong, but a merged
list would be nice as a 3rd option.
> This is great, if you are interested I could set you up as an
> contributor on the github organization and you could push your changes
> to the use-mail branch. With your changes and especially if we get
> crypto working on Mail I would switch completely as well.
let me work on my own repo for a while, as i am quite new to ruby, learning it
as i go along, so i don't feel confident to make commits without anyone
reviewing them. (actually, i think, if at all possible any commit to a project
should be reviewed by at least one other person)
but thanks for the offer. i am sure in time we'll see
whether my work is good enough.
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/
next prev parent reply other threads:[~2014-04-01 4:13 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 [this message]
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
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=1396324522-sup-8837@email.archlab.tuwien.ac.at \
--to=mbaehr@email.archlab.tuwien.ac.at \
--cc=eg@gaute.vetsj.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