From: Samuel Padgett <samuel.padgett@gte.net>
Subject: Re: Wizards (was: Re: Oort Version)
Date: 28 Mar 2001 14:03:07 -0500 [thread overview]
Message-ID: <877l1990no.fsf@harpo.homeip.net> (raw)
In-Reply-To: <rj3dby2dv3.fsf_-_@ssv2.dina.kvl.dk> (Per Abrahamsen's message of "28 Mar 2001 15:59:44 +0200")
Per Abrahamsen <abraham@dina.kvl.dk> writes:
> The Right Thing(TM) is to write in custom-file, and leave .gnus for
> manual customization.
The Viper package has a some simple invoked-for-the-first-time
messages and prompts for new Viper users. It writes settings to
~/.viper rather than `custom-file'. I'm not saying this is the Right
Thing, but it would be nice to see consistency between packages that
perform first-time initialization, particularly those packages that
are a part of do Emacs.
I'm not sure how Viper knows whether it's being invoked for the first
time. Maybe through the abscence of ~/.viper?
Sam
--
Room service? Send up a larger room.
-- Groucho Marx
prev parent reply other threads:[~2001-03-28 19:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 19:00 Oort Version 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
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 [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=877l1990no.fsf@harpo.homeip.net \
--to=samuel.padgett@gte.net \
/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).