Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Gnus-ances
Date: 14 Apr 2001 13:35:13 +0200	[thread overview]
Message-ID: <m3k84oee9x.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <rjsnjhqbdw.fsf@ssv2.dina.kvl.dk>

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> > I can almost envision a general framework for Emacs wizards.  It's
> > mainly a tree of options for the user to navigate through, right? 
> 
> That sounds more like customize.

Well, not all that much.  A wizard usually guides people through a
series of actions.  Say, the user says that she wishes to use pop for
fetching mail, and the wizard then asks "which pop server?"  If the
user said "fetch from the local spool", then the wizard would check
whether /var/spool/mail is there, and suggest that instead.  And so
on.

Customize lets you find your own way through the options.  A wizard
only lets you take certain steps, in (what it considers) proper order.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen


       reply	other threads:[~2001-04-14 11:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Xns907E6CBB2555Fraravistutopiacom@127.0.0.1>
     [not found] ` <yld7amoxq3.fsf@windlord.stanford.edu>
     [not found]   ` <Xns907E7A3B6C0B7raravistutopiacom@127.0.0.1>
     [not found]     ` <vxksnjiyngj.fsf@cinnamon.vanillaknot.com>
     [not found]       ` <Xns907E9EFF084ABraravistutopiacom@127.0.0.1>
     [not found]         ` <td4cu6lchtb29e@news.supernews.com>
     [not found]           ` <vxkd7alzgxt.fsf@cinnamon.vanillaknot.com>
     [not found]             ` <m3n19pl34x.fsf@quimbies.gnus.org>
     [not found]               ` <rjsnjhqbdw.fsf@ssv2.dina.kvl.dk>
2001-04-14 11:35                 ` Lars Magne Ingebrigtsen [this message]
2001-04-14 13:34                   ` Gnus-ances Harry Putnam

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=m3k84oee9x.fsf@quimbies.gnus.org \
    --to=larsi@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).