From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Illogical use of gnus-novice-user & gnus-expert-user
Date: 26 Oct 2004 11:14:19 -0400 [thread overview]
Message-ID: <4nu0shqzp0.fsf@lifelogs.com> (raw)
In-Reply-To: <y8hxwlhk.fsf@gmail.com> (Cheng Gao's message of "Sat, 23 Oct 2004 22:35:35 +0800")
On Sat, 23 Oct 2004, chenggao@gmail.com wrote:
> Attached is a patch file based on latest No Gnus cvs code.
>
> My idea is to remove gnus-novice-user and use gnus-expert-user only.
>
> Gnus developers, if you think it's of any meaning, please take some time
> to look into it.
I looked at the patch and it's fine for its purpose.
I'm not sure I agree with the purpose, though. It's possible to be
more than a novice but less than an expert. I would make
gnus-user-expertise-level either 'novice, 'expert, or nil (the
default, indicating general awareness with cautious exploration of
advanced Gnus features). Then I would use gnus-user-expertise-level
everywhere; for ease of use I would also provide the functions
gnus-novice-user and gnus-expert-user that are drop-in replacements
for the variables we currently use.
Ted
prev parent reply other threads:[~2004-10-26 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 7:17 Cheng Gao
2004-10-23 14:35 ` Cheng Gao
2004-10-26 15:14 ` Ted Zlatanov [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=4nu0shqzp0.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).