From: "Jochen Küpper" <jochen@jochen-kuepper.de>
Cc: ding@gnus.org
Subject: Re: nnimap problems
Date: Thu, 27 Mar 2003 23:51:20 +0100 [thread overview]
Message-ID: <86vfy4mniv.fsf@jochen.rijnh.nl> (raw)
In-Reply-To: <86k7eq402b.fsf@jochen.rijnh.nl> (Jochen =?iso-8859-1?q?K=FCpper's?= message of "Sun, 23 Mar 2003 15:41:48 +0100")
The following message is a courtesy copy of an article
that has been posted to gnu.emacs.gnus as well.
On Sun, 23 Mar 2003 15:41:48 +0100 Jochen Küpper wrote:
Jochen> I just realize that my IMAP groups also don't have "coding":(
Jochen> That is, all articles a "greenish" in the summary buffer, no
Jochen> matter what marks they have. (Normally "O" is blueish, ticked
Jochen> is red, ...)
On Thu, 27 Mar 2003 16:20:00 -0600 Kevin Greiner wrote:
Kevin> Steven E. Harris <seharris@raytheon.com> writes:
>> Is there some way to get the header caching benefits of the agent
>> without sacrificing the existing summary buffer information? For
>> example, I consider a message being ticked or having been read to
>> take precedence over whether or not it's been downloaded.
Kevin> I suspect that your views concerning precidence are driven by
Kevin> the fact that your agentizing an existing group. However, gnus
Kevin> aims to please all, so try customizing gnus-summary-highlight.
Kevin> All that you need do is delete the three cons cells whose cdr
Kevin> name a gnus*undownloaded-face.
Works for me:) Thanks.
Greetings,
Jochen
--
Einigkeit und Recht und Freiheit http://www.Jochen-Kuepper.de
Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D
Sex, drugs and rock-n-roll
prev parent reply other threads:[~2003-03-27 22:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 16:02 IMAP deleting mails Jochen Küpper
2003-03-23 13:25 ` Kai Großjohann
2003-03-23 14:41 ` nnimap problems (was: deleting mails) Jochen Küpper
2003-03-24 21:11 ` nnimap problems Kai Großjohann
2003-03-25 7:52 ` Niklas Morberg
2003-03-27 18:15 ` Jochen Küpper
2003-03-27 22:51 ` Jochen Küpper [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=86vfy4mniv.fsf@jochen.rijnh.nl \
--to=jochen@jochen-kuepper.de \
--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).