From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Marking articles after bb493e5
Date: Wed, 16 Feb 2011 12:42:08 -0800 [thread overview]
Message-ID: <87r5b7sodb.fsf@gnus.org> (raw)
In-Reply-To: <87lj1ivw6n.fsf@gmail.com>
Raphael Kubo da Costa <kubito@gmail.com> writes:
> Things seem to work fine again when I set gnus-propagate-marks to t. Am
> I missing something here?
Sorry! I don't know what I was thinking... I've now flipped that
variable to nil again.
I think what I was after was trying to avoid having the -marks functions
called by default on backends like nntp, which isn't very useful. (And
it's slow.) But, of course, this made the marks functions not being
called on nnimap, too, so I'll have to find a different way to do that.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2011-02-16 20:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 3:00 Raphael Kubo da Costa
2011-02-15 13:06 ` Tassilo Horn
2011-02-16 20:42 ` Lars Ingebrigtsen [this message]
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=87r5b7sodb.fsf@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).