From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: updating backend marks immediately
Date: Tue, 09 Nov 2010 16:01:55 -0600 [thread overview]
Message-ID: <87wromp358.fsf@lifelogs.com> (raw)
In-Reply-To: <87pquku8wi.fsf@uwo.ca>
On Thu, 04 Nov 2010 16:32:45 -0400 Dan Christensen <jdc@uwo.ca> wrote:
DC> I'd like to update the marks on my imap server whenever they change in
DC> an nnimap summary buffer. This seems to do the trick:
DC> (add-hook 'gnus-summary-update-hook 'gnus-summary-update-info)
DC> It updates the imap server, but doesn't save the .newsrc or the dribble
DC> file, so it's quick.
DC> I'm posting this in case it is useful to others, but also to check that
DC> it is safe. Could Gnus get confused by this? Would it be better to call
DC> (gnus-summary-save-newsrc)
DC> which also saves the information to the dribble buffer and saves the
DC> dribble file?
I would find it surprising if `Q' didn't work. I think your change
would break that.
Ted
next prev parent reply other threads:[~2010-11-09 22:01 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 [this message]
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
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=87wromp358.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).