Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: "Philipp Überbacher" <murks@lavabit.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] unread status
Date: Tue, 29 Dec 2009 14:45:38 +0100	[thread overview]
Message-ID: <1262093816-sup-8151@tw> (raw)

Hi,
during the last couple of days I managed to get sup up and running,
using ruby 1.8.7, xapian, msmtp and offlineimap.

Now that I use it I noticed strange behavior regarding unread messages.
It works like this:

New messages in the inbox, I read through them, hitting 'a'.
The messages vanish from the Inbox. So far so good.

I hit 'L' 'Enter' and notice that all messages I just read are listed as
unread. I navigate to unread, read the messages again and hit 'a'. Now
they aren't marked as unread anymore.

Also, when I read them in the inbox and they are still labeled unread
and I restart sup they aren't labeled unread anymore.

Well, expected behavior is to have them labeled read after I read them,
obviously.



I experienced something similar when I used the built-in imap support.
There it wouldn't really Poll when I hit P, new messages only showed up
after I restarted sup.


Either these are bugs or I don't get how sup works,
either way, help is appreciated.

Regards,
Philipp

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


             reply	other threads:[~2010-01-03 22:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29 13:45 Philipp Überbacher [this message]
2009-12-29 14:47 Philipp Überbacher
2009-12-29 22:53 ` William Morgan
2009-12-29 23:12   ` Philipp Überbacher
2009-12-29 23:24     ` Tero Tilus
2009-12-29 23:49       ` Rich Lane
2009-12-29 23:54         ` William Morgan
2009-12-30  0:32           ` John Bent
2010-01-03 22:22             ` William Morgan
2010-03-05 15:59               ` John Bent
2010-03-05 20:00                 ` John Bent
2010-03-05 20:32                   ` John Bent
2009-12-29 23:33     ` William Morgan
2009-12-29 23:54       ` Philipp Überbacher

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=1262093816-sup-8151@tw \
    --to=murks@lavabit.com \
    --cc=sup-talk@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