Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: Damien Leone <damien.leone@fensalir.fr>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Strange maildir/OfflineImap/maildir-sync behavior
Date: Thu, 20 Jan 2011 05:53:36 -0500	[thread overview]
Message-ID: <1295520737-sup-176@ezyang> (raw)
In-Reply-To: <1295471328-sup-9770@mailer>

I have a theory for why this occurs: when we mark mail read on maildir,
it gets moved from new to cur, IIRC? So if Sup's state doesn't get
adequately updated, an old buffer could try to look at the old location.
This should be easily verifiable by looking at the console messages.

Edward
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


  reply	other threads:[~2011-01-20 11:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 14:08 Edward Z. Yang
2011-01-19 20:01 ` Roni Choudhury
2011-01-19 20:33   ` Edward Z. Yang
2011-01-19 21:10   ` Damien Leone
2011-01-20 10:53     ` Edward Z. Yang [this message]
2011-01-19 21:12 ` Damien Leone
2011-01-20  2:55 ` Edward Z. Yang

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=1295520737-sup-176@ezyang \
    --to=ezyang@mit.edu \
    --cc=damien.leone@fensalir.fr \
    --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