From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Terminology
Date: Wed, 21 Apr 2004 11:50:03 -0400 [thread overview]
Message-ID: <4nvfjtgwk4.fsf@lifelogs.com> (raw)
In-Reply-To: <87oepos7w0.fsf@emptyhost.emptydomain.de> (Kai Grossjohann's message of "Mon, 19 Apr 2004 10:13:03 +0200")
On Mon, 19 Apr 2004, kai@emptydomain.de wrote:
> I'm not sure that we want to document "`read' is ambiguous". I
> guess that it would be much better to avoid ambiguity.
It's obvious some sort of clarification would be useful.
Let's not confuse the terminology of marks with the terminology of
articles - e.g. there's no "unread" mark but there are unread
articles. Maybe the two terminologies should be clearly separated but
in the same section.
Additionally, it may be confusing to non-native English speakers that
the word "read" is both the present tense and past tense of the verb
"to read," in addition to being an adjective. Unfortunately English
is full of these ambiguities.
Ted
next prev parent reply other threads:[~2004-04-21 15:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 9:05 Configuring spam.el: A few questions Jonas Steverud
2004-03-31 18:54 ` Ted Zlatanov
2004-04-03 11:57 ` Jonas Steverud
2004-04-15 19:54 ` Ted Zlatanov
2004-04-16 9:42 ` Jonas Steverud
2004-04-16 14:36 ` Ted Zlatanov
2004-04-16 20:37 ` Kai Grossjohann
2004-04-17 9:28 ` Jonas Steverud
2004-04-17 18:55 ` Dan Christensen
2004-04-18 8:04 ` Kai Grossjohann
2004-04-18 17:37 ` Dan Christensen
2004-04-18 19:56 ` Terminology (was: Configuring spam.el: A few questions) Jonas Steverud
2004-04-18 20:16 ` Terminology Simon Josefsson
2004-04-18 20:28 ` Terminology Jonas Steverud
2004-04-18 20:50 ` Terminology Simon Josefsson
2004-04-19 8:13 ` Terminology Kai Grossjohann
2004-04-21 15:50 ` Ted Zlatanov [this message]
2004-04-18 20:30 ` Configuring spam.el: A few questions Kai Grossjohann
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=4nvfjtgwk4.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).