From: Stefan Kangas <stefankangas@gmail.com>
To: Simon Pugnet <simon@polaris64.net>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Propose to add setup-wizard.el to ELPA
Date: Sun, 2 Jan 2022 13:49:54 -0500 [thread overview]
Message-ID: <CADwFkm=d--wdt_wSFm20tYQaE6_iWbf9fCY7mF1n=Z2ziDDrKw@mail.gmail.com> (raw)
In-Reply-To: <87k0fit5eo.fsf@polaris64.net>
Simon Pugnet <simon@polaris64.net> writes:
> If the wizard could provide a common interface (e.g. a "wizard-builder")
> that's easy to use and is presented using the same interface as the main
> wizard then I think that could be a very nice way of helping newcomers
> to certain packages.
We have discussed this in the past, and I can only very much agree.
> For example, as well as giving configuration instructions in the
> package's README, the package author could include their own wizard and
> say something like "For interactive configuration, just evaluate
> (invoke-wizard 'some-package) after loading the package."
Or you could run the wizard if you detect that the package has not
already been configured. I guess this would be up to the package
developer to decide what will work best for their package.
> One could argue that this is pretty close to just launching
> customize-group for the package and limiting the options to only the
> most important. However Yuan's wizard provides a more newcomer-friendly
> and interactive interface (e.g. changing the theme immediately once it
> is selected) so I think it is worthwhile keeping the wizard UI and
> customize UI separate in this case.
Right. The problem with customize-group is that it can easily be
overwhelming, as it shows all options with their full documentation,
instead of just asking a small set of highly specific questions like
"what's the address of your mail server".
next prev parent reply other threads:[~2022-01-02 18:49 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 17:26 Propose to add setup-wizard.el to ELPA Simon Pugnet
2022-01-02 18:49 ` Stefan Kangas [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-02 15:46 Simon Pugnet
2022-01-02 2:07 Yuan Fu
2022-01-02 2:37 ` Po Lu
2022-01-02 3:02 ` Yuan Fu
2022-01-02 3:22 ` Po Lu
2022-01-02 5:51 ` Yuan Fu
2022-01-02 6:30 ` Po Lu
2022-01-02 7:58 ` Yuan Fu
2022-01-02 8:07 ` Po Lu
2022-01-02 9:07 ` Yuan Fu
2022-01-02 9:22 ` xenodasein--- via Emacs development discussions.
2022-01-02 9:45 ` Eduardo Ochs
2022-01-02 9:45 ` Po Lu
2022-01-02 10:09 ` Eduardo Ochs
2022-01-02 10:15 ` Po Lu
2022-01-02 10:25 ` Eduardo Ochs
2022-01-02 10:34 ` xenodasein--- via Emacs development discussions.
2022-01-02 10:52 ` Eli Zaretskii
2022-01-02 10:57 ` xenodasein--- via Emacs development discussions.
2022-01-02 11:14 ` Eli Zaretskii
2022-01-02 11:30 ` xenodasein--- via Emacs development discussions.
2022-01-02 11:38 ` Eli Zaretskii
2022-01-02 12:01 ` Po Lu
2022-01-02 11:31 ` xenodasein--- via Emacs development discussions.
[not found] ` <CADs++6jtFBah1hhsuN6T_-kFyjc_pNmmVKA+16vOWa8OctOZLw@mail.gmail.com>
2022-01-02 11:02 ` xenodasein--- via Emacs development discussions.
2022-01-02 11:17 ` Po Lu
2022-01-02 11:36 ` xenodasein--- via Emacs development discussions.
2022-01-02 12:03 ` Po Lu
2022-01-02 15:27 ` Stefan Kangas
[not found] ` <MsPZqa9--3-2@tutanota.de-MsP_1xO----2>
2022-01-02 11:57 ` xenodasein--- via Emacs development discussions.
2022-01-02 12:05 ` Po Lu
2022-01-02 15:27 ` Stefan Kangas
2022-01-02 15:37 ` Eli Zaretskii
2022-01-02 16:43 ` xenodasein--- via Emacs development discussions.
2022-01-02 17:32 ` Stefan Kangas
2022-01-03 0:42 ` Po Lu
2022-01-02 11:58 ` Philip Kaludercic
2022-01-07 10:09 ` Jean Louis
2022-01-02 9:41 ` Po Lu
2022-01-02 17:18 ` Yuan Fu
2022-01-07 10:02 ` Jean Louis
2022-01-07 10:50 ` Po Lu
2022-01-07 12:11 ` Eli Zaretskii
2022-01-09 22:54 ` Yuan Fu
2022-01-10 4:15 ` Jean Louis
2022-01-10 17:24 ` Eli Zaretskii
2022-01-11 4:47 ` Jean Louis
2022-01-11 4:51 ` Richard Stallman
2022-01-02 7:55 ` Eli Zaretskii
2022-01-02 8:07 ` Yuan Fu
2022-01-02 15:42 ` Stefan Kangas
2022-01-02 17:26 ` Yuan Fu
2022-01-02 17:36 ` xenodasein--- via Emacs development discussions.
[not found] ` <MsQrOAf--J-2@tutanota.de-MsQrQR2----2>
2022-01-02 17:55 ` xenodasein--- via Emacs development discussions.
2022-01-02 18:50 ` Stefan Kangas
2022-01-02 21:14 ` Yuan Fu
2022-01-03 0:45 ` Po Lu
2022-01-03 0:59 ` Yuan Fu
2022-01-03 1:02 ` Stefan Kangas
2022-01-03 9:12 ` Joost Kremers
2022-01-03 12:49 ` Eli Zaretskii
2022-01-03 13:00 ` Po Lu
2022-01-03 19:30 ` Joost Kremers
2022-01-02 8:07 ` Po Lu
2022-01-02 15:23 ` nanjunjie
2022-01-03 8:28 ` Philip Kaludercic
2022-01-04 16:09 ` Nan JunJie
2022-01-04 19:45 ` Philip Kaludercic
2022-01-02 12:02 ` Philip Kaludercic
2022-01-07 9:58 ` Jean Louis
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='CADwFkm=d--wdt_wSFm20tYQaE6_iWbf9fCY7mF1n=Z2ziDDrKw@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=simon@polaris64.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.