From: Simon Josefsson <jas@extundo.com>
Subject: Re: What's the difference between gnus-recent-mark and gnus-unseen-mark?
Date: Tue, 10 Sep 2002 11:56:54 +0200 [thread overview]
Message-ID: <ilu3csimal5.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87elc32mzm.fsf@harris.sdo.us.ray.com>
Steven E. Harris <seharris@raytheon.com> writes:
>> This is fine (but I could agree N is a bit noicy, what
>> about using `,' instead?).
>
> The comma could be fine. As the semantic distinction is subtle (at
> least in my usage scenario), the mark distinction should be subtle as
> well.
I've been running with , for some hours now and it could work,
although it looks a bit unprofessional. Colon : might look better.
OTOH I now remember why N was chosen -- Pine uses this as a new mail
indicator, and perhaps Mutt also does the same.
>> When I have read IMAP mail using another IMAP mail reader (I often
>> read via Squirrelmail web mail) I don't get the N but I do get a
>> . instead.
>
> So is the dot indicating that while the message may have been seen
> before elsewhere, this Gnus instance hasn't seen it yet?
Yes. "seen elsewhere" is defined by the server, and can be anything.
> The 'N' would mean that no client has seen the message, while the
> dot would mean that Gnus hasn't seen it. Is that correct?
Yes, although a N might be displayed even if the mail is old if the
server is buggy or has a weird policy. Gnus doesn't control it.
>> Perhaps the documentation could be improved to convey this stuff in
>> a clearer way. Suggestions?
>
> I can't propose specific wording right now, but these points should be
> made manifest (provided they are correct):
>
> o Have each mark's documentation mention the other, explaining how
> they differ.
> o Explain the difference in "scope" between the marks. One addresses
> message state across multiple clients, while the other is relevant
> only to this client.
I improved it a little, but didn't explain the multi-client issue
since I couldn't come up with a brief and concise explanation.
next prev parent reply other threads:[~2002-09-10 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 16:14 Steven E. Harris
2002-09-08 15:30 ` Simon Josefsson
[not found] ` <vafofb82ota.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <ilu65xg2jp8.fsf@latte.josefsson.org>
2002-09-09 9:55 ` Kai Großjohann
[not found] ` <87elc32mzm.fsf@harris.sdo.us.ray.com>
2002-09-10 9:56 ` Simon Josefsson [this message]
2002-09-10 12:53 ` Kai Großjohann
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=ilu3csimal5.fsf@latte.josefsson.org \
--to=jas@extundo.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).