From: Colin Marquardt <colin.marquardt@usa.alcatel.com>
Subject: Re: Oort Version
Date: 27 Mar 2001 16:38:01 -0800 [thread overview]
Message-ID: <ysd61yrihgnq.fsf@sol-cmarquar.pet.usa.alcatel.com> (raw)
In-Reply-To: <vxkvgoueons.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "27 Mar 2001 19:13:27 -0500")
Karl Kleinpaste <karl@charcoal.com> writes:
> Customize is good, but I would really like to see...
>
> - A set of functions named things like gnus-init-very-first-time,
> gnus-init-mail, gnus-init-topics. And then have Gnus use these
> functions based on obvious criteria. For example, the lack of any
> .gnus would be a firm indicator of a need for gnus-init-first-time,
> where the user would be queried for the name of his NNTP server, set
> up authinfo if needed, and perhaps be asked if there are any groups
> he'd like to see immediately subscribed. Maybe bring up an explanatory
emacro.el has some stuff like this, though not specifically targeted
to Gnus. And I really like the whole idea.
Colin
next prev parent reply other threads:[~2001-03-28 0:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 19:00 Jake Colman
2001-03-26 20:05 ` Kai Großjohann
2001-03-26 20:29 ` Karl Kleinpaste
2001-03-27 21:02 ` Simon Josefsson
2001-03-27 21:33 ` Steven E. Harris
2001-03-27 22:29 ` Robin S. Socha
2001-03-28 0:13 ` Karl Kleinpaste
2001-03-28 0:38 ` Colin Marquardt [this message]
2001-03-28 18:06 ` Josh Huber
2001-03-28 3:40 ` Simon Josefsson
2001-03-28 18:51 ` Samuel Padgett
2001-03-28 7:13 ` Christoph Conrad
2001-03-28 7:13 ` Christoph Conrad
2001-03-28 7:15 ` Christoph Conrad
2001-03-28 7:21 ` Christoph Conrad
2001-03-28 8:43 ` Christoph Conrad
2001-03-28 13:59 ` Wizards (was: Re: Oort Version) Per Abrahamsen
2001-03-28 14:47 ` Karl Kleinpaste
2001-03-28 15:58 ` Per Abrahamsen
2001-03-28 16:34 ` Paul Jarc
2001-03-28 22:38 ` Alex Schroeder
2001-03-28 19:03 ` Samuel Padgett
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=ysd61yrihgnq.fsf@sol-cmarquar.pet.usa.alcatel.com \
--to=colin.marquardt@usa.alcatel.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).