From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: updating backend marks immediately
Date: Wed, 24 Nov 2010 22:46:47 +0100 [thread overview]
Message-ID: <m3oc9e9yyg.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87fwuq4d15.fsf@uwo.ca>
Dan Christensen <jdc@uwo.ca> writes:
>> It occurs to me that I should probably have do it the other way around.
>> That is, set the marks on the article before moving it, and then not
>> bother to copy over the marks afterwards. The result should be much the
>> same, but slightly more secure if something fails in the middle.
>
> I think what you propose might be better.
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.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-11-24 21:46 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 [this message]
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
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=m3oc9e9yyg.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).