Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Welsh Duggan <mwd@cert.org>
To: Michael Welsh Duggan <md5i@md5i.com>
Cc: ding@gnus.org
Subject: Re: searching by Message-ID after copy/move; speeding things up
Date: Thu, 14 Jun 2012 15:51:05 -0400	[thread overview]
Message-ID: <tntpq91wu3a.fsf@waterbuck.yellow.cert.org> (raw)
In-Reply-To: <877gvamhzv.fsf@zelenka.enovance.com> (Julien Danjou's message of "Thu, 14 Jun 2012 10:10:12 +0200")

Julien Danjou <julien@danjou.info> writes:

> On Thu, Jun 14 2012, Michael Welsh Duggan wrote:
>
>> The change was quite simple, and most of my time was spent re-learning
>> how the nnimap library does things in general.  I hope that something
>> like this can make it into mainline Gnus.
>
> Attached is an experimental patch. Could you test it and tell me if this
> resolve your problem?

I'm afraid not.  In some (but not all) instances the moved message
doesn't show up as RECENT.  (More specifically, UID SEARCH RECENT fails
to locate them.)  FWIW, RECENT doesn't seem to be very well specified in
the IMAP spec, either:

http://mail-archives.apache.org/mod_mbox/james-server-dev/200803.mbox/%3C88f6e29a0803210110x2784101crf66e32fd96fd1b7f@mail.gmail.com%3E

-- 
Michael Welsh Duggan
(mwd@cert.org)



  reply	other threads:[~2012-06-14 19:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  4:42 Michael Welsh Duggan
2012-06-14  8:10 ` Julien Danjou
2012-06-14 19:51   ` Michael Welsh Duggan [this message]
2012-06-14 19:59     ` Julien Danjou
2012-06-14 20:11       ` Michael Welsh Duggan
2012-06-15 14:17         ` Julien Danjou
2012-06-15 15:11           ` Michael Welsh Duggan
2012-06-19  8:53             ` Julien Danjou
2012-06-19 15:33               ` Michael Welsh Duggan
2012-06-25 11:23                 ` Julien Danjou
2012-06-25 14:00                   ` Michael Welsh Duggan

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=tntpq91wu3a.fsf@waterbuck.yellow.cert.org \
    --to=mwd@cert.org \
    --cc=ding@gnus.org \
    --cc=md5i@md5i.com \
    /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;
as well as URLs for NNTP newsgroup(s).