Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: updating backend marks immediately
Date: Thu, 25 Nov 2010 10:28:30 -0500	[thread overview]
Message-ID: <87tyj5h17l.fsf@uwo.ca> (raw)
In-Reply-To: <m3zksy8jkn.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> Yeah, I'm attempting to do that now, but it isn't totally trivial.
>> There's apparently no single function to just sync all the (current)
>> flags from a single article to the backend?  So I think I'll have to
>> write that first.
>
> Done.  It was kinda trivial, really.  So it now ensures that all marks
> are set before issuing the COPY command.

Thanks!  It looks like an extra STORE command is being done, though.
Below is an example where I didn't change the marks on an article before
moving it (from "test" to the same group), and yet the first line shows
a bunch of flags being removed.  And I don't know why \Seen would be
removed, since the article was marked as read.  Then in command 308, the
\Seen flag is restored, which seems inefficient.

And are commands 309 and 310 needed?

Dan

10:14:38 302 UID STORE 10719 -FLAGS.SILENT (\Seen \Flagged \Answered
gnus-expire gnus-dormant gnus-save gnus-download gnus-forward)

10:14:38 303 UID FETCH 10719 (UID RFC822.SIZE BODYSTRUCTURE
BODY.PEEK[HEADER.FIELDS (Subject From Date Message-Id References
In-Reply-To Xref X-Spam-Status To Cc Keywords Newsgroups Subject)])

10:14:38 304 UID COPY 10719 "test"

10:14:38 305 UID STORE 10719 +FLAGS.SILENT (\Deleted)

10:14:38 306 UID EXPUNGE 10719

10:14:38 307 UID SEARCH HEADER Message-Id
"<2A24BF61-650C-468E-B14C-D9351659FACD@birs.ca>"

10:14:38 308 UID STORE 10728 +FLAGS.SILENT (\Seen)

10:14:38 309 SELECT "test"

10:14:38 310 UID FETCH 1:* FLAGS





  parent reply	other threads:[~2010-11-25 15:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04 20:32 Dan Christensen
2010-11-04 20:37 ` Lars Magne Ingebrigtsen
2010-11-09 22:01 ` Ted Zlatanov
2010-11-10  1:13   ` Dan Christensen
2010-11-10 13:16     ` Ted Zlatanov
2010-11-10 21:00       ` Lars Magne Ingebrigtsen
2010-11-12 23:54       ` Dan Christensen
2010-11-14 15:58         ` Lars Magne Ingebrigtsen
2010-11-14 21:47           ` Dan Christensen
2010-11-21  5:31             ` Lars Magne Ingebrigtsen
2010-11-21  5:38               ` Lars Magne Ingebrigtsen
2010-11-22  1:45                 ` Dan Christensen
2010-11-22  1:48                   ` Lars Magne Ingebrigtsen
2010-11-24 21:39                     ` Dan Christensen
2010-11-24 21:46                       ` Lars Magne Ingebrigtsen
2010-11-24 22:04                         ` Lars Magne Ingebrigtsen
2010-11-25 12:00                           ` Steinar Bang
2010-11-25 14:28                             ` Lars Magne Ingebrigtsen
2010-11-25 14:40                               ` Steinar Bang
2010-11-25 15:28                           ` Dan Christensen [this message]
2010-12-05 14:39                             ` Lars Magne Ingebrigtsen
2010-12-05 15:22                               ` Dan Christensen

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=87tyj5h17l.fsf@uwo.ca \
    --to=jdc@uwo.ca \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).