unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Subject: Ok, I have had it.  A proposal for wizards.
Date: 02 Jan 2004 04:28:42 +0100	[thread overview]
Message-ID: <x5fzezav11.fsf@lola.goethe.zz> (raw)


Emacs comes bundled with a whole lot of packages that are not loaded
by default.  The typical scene when somebody complains to a guru "it
would be so convenient if Emacs could do such-and-such" is "well,
have you enabled/configured this-and-that?" -- blank stare.

So what to do about that?  Wizards.  A wizard is a human-friendly
walk-through through some configuration issue.

A package registers for wizards in manner similar to autoload cookies
(we usually want neither the package nor its wizard loaded unless the
user is actually going to configure anything), and it will usually
register for a major mode instead of a function call.  Now we get a
"wizard" menu with unexamined goodies highlighted, and a conditional
magic wand toolbar button that appears whenever any goody for the
current major mode has not yet been examined.  The autoload
cookie-like thing will be enough to provide a title line such as

RefTeX  Manage Crossreferences, Indexes and tocs in TeX modes
[Mark as Seen] [Configure] [Info]

When I press [Mark as Seen], this means the obvious thing (it will
register the fact in a customized variable or something).  When I
press [Info], I get the manual, when I press [Configure], I enter a
dialog with explanations of what the stuff does and Yes/No questions
and the most important customizable variables.  This dialog will
obviously be stored in a file of its own so as to be only loaded when
needed (usually once per user).  When new packages get installed
side-wide, appropriate wizard entries would want to get added in order
to notify the users that new features are available.

I mean, take a look alone at the minibuffer-related modes: we have
oodles of useful things like iswitchb-mode, file-name-shadow-mode,
minibuffer-electric-default-mode and so on.  Nobody ever uses them
because nobody knows about them.  And would have to read info pages
in order to find out more, and follow the instructions in each of
those different files for switching the feature on, and so forth and
so on.  Too much trouble.

Advanced modes (like AUCTeX or cperl-mode or so) would register their
wizards also in the modes they are supposed to supplant.  That way
people would be notified if superior or different alternatives were
available.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

             reply	other threads:[~2004-01-02  3:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02  3:28 David Kastrup [this message]
2004-01-02  9:20 ` Ok, I have had it. A proposal for wizards Eli Zaretskii
2004-01-02 11:02   ` David Kastrup
2004-01-02 14:27   ` Danilo Segan
2004-01-02 15:33     ` David Kastrup
2004-01-03  2:43     ` Miles Bader
2004-01-04  3:52 ` Richard Stallman
2004-01-04  5:48   ` David Kastrup

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x5fzezav11.fsf@lola.goethe.zz \
    --to=dak@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).