From: "Bruno Hertz" <spammer.go.home@gmail.com>
Subject: Re: Emacs CVS, question regarding ticked, dormant, \Flagged with nnimap.
Date: Mon, 28 Mar 2005 18:55:19 +0200 [thread overview]
Message-ID: <m3zmwnsoaw.fsf@caruso.quasi.local> (raw)
In-Reply-To: <m3sm2g6ccc.fsf@caruso.quasi.local>
"Bruno Hertz" <spammer.go.home@gmail.com> writes:
> Two solutions come to mind: redefine gnus-article-mark-lists, which
> would be somewhat arbitrary and maybe invite for future mistakes, or
> sort the actions in nnimap-request-set-mark to do deletes first.
OK, for the records, as a quick fix I put the following into my .gnus:
(defun nnimap-mark-action-is-less-p (a b)
(if (and (eq (nth 1 a) 'del) (eq (nth 1 b) 'add)) t nil))
(defadvice nnimap-request-set-mark
(before nnimap-request-set-mark-sort-actions
(group actions &optional server) activate compile)
(setq actions (sort actions 'nnimap-mark-action-is-less-p)))
Regards, Bruno.
prev parent reply other threads:[~2005-03-28 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 15:47 Bruno Hertz
2005-03-27 17:50 ` Bruno Hertz
2005-03-27 20:52 ` Bruno Hertz
2005-03-28 16:55 ` Bruno Hertz [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=m3zmwnsoaw.fsf@caruso.quasi.local \
--to=spammer.go.home@gmail.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).