From: Simon Josefsson <jas@extundo.com>
Subject: Re: Terminology
Date: Sun, 18 Apr 2004 22:50:10 +0200 [thread overview]
Message-ID: <iluzn99ko3h.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m2hdvhm3ou.fsf@c-ec5372d5.036-4-67626721.cust.bredbandsbolaget.se>
Jonas Steverud <tvrud@bredband.net> writes:
> Previous mails has indicated that there are some confusion regarding
> what we call an article - sometimes regardless of the actual marks of
> it and sometimes the marks are considered - and I just tries to see if
> we can do something about that confusion. Renaming some of the terms
> might help.
Or perhaps just document the current terms some more...
Perhaps what the manual need are short, self-contained, sections
focused on particular topic. I have been thinking about writing a
"Non-ASCII survival guide" node with all variables (Gnus + Message,
sending and receiving, etc) a few times, but couldn't figure out how
to write it in a style that would blend in. "Non-ASCII" is perhaps a
too large topic, but a "Marks & Flags survival guide" section might be
more appropriate.
next prev parent reply other threads:[~2004-04-18 20: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 ` Simon Josefsson [this message]
2004-04-19 8:13 ` Terminology Kai Grossjohann
2004-04-21 15:50 ` Terminology Ted Zlatanov
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=iluzn99ko3h.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).