From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Dormant and ticked not independent in nnimap?
Date: Wed, 04 Jul 2001 12:13:03 +0200 [thread overview]
Message-ID: <vafelrxhuj4.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <ilu1ynxjazw.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Wed, 04 Jul 2001 11:32:03 +0200")
On Wed, 04 Jul 2001, Simon Josefsson wrote:
> Yes, uhm, nnimap translates "dormant" into \Flagged + gnus-dormant.
> This is so the article "stand out" when you're using some other IMAP
> client.
>
> The flag is added at line ~943, and removed internally at line ~910.
> It should be easy to comment this two parts out. Maybe I should
> make this conditional, so you can disable this behaviour?
If you would do that, that would be wonderful.
> Btw, very interesting idea! This is a nice way to get user-specific
> flags without server support for the idea. It might even be
> possible to extend to all flag (i.e. different set of Read-flags for
> different users).
Could be. Never thought about that. Might be useful in some
circumstances.
>> Is there anything I can do about this? Or do I have to wait for
>> Cyrus 2.x to get per-user article marks?
>
> I'm not sure if even Cyrus 2.x helps. \Read and maybe some other
> are user-specific, but I don't think \Flagged etc are. But I maybe
> wrong.
Well, \Read is user-specific even in the old 1.6.x. Since I don't
really have 2.x yet, I'm not _sure_ which ones will be user-specific
then.
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2001-07-04 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-04 8:08 Kai Großjohann
2001-07-04 9:32 ` Simon Josefsson
2001-07-04 10:13 ` Kai Großjohann [this message]
2001-07-04 17:44 ` Simon Josefsson
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=vafelrxhuj4.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).