From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Propose to add setup-wizard.el to ELPA
Date: Sun, 02 Jan 2022 09:55:06 +0200 [thread overview]
Message-ID: <83mtkeefmt.fsf@gnu.org> (raw)
In-Reply-To: <897ED591-43BC-4029-912A-917E5E9F6930@gmail.com> (message from Yuan Fu on Sat, 1 Jan 2022 18:07:53 -0800)
> From: Yuan Fu <casouri@gmail.com>
> Date: Sat, 1 Jan 2022 18:07:53 -0800
>
> A while ago I wrote a package that helps a new user to configure Emacs: it takes a user through some interactive pages, where changes takes effect immediately; and in the end it generates some code that can be copied to init.el.
>
> Demo for the original package: https://youtu.be/0qMskTAR2aw
>
> I made some improvements to that package and renamed it setup-wizard. Do you think we could add it to ELPA? Maybe the name is too “official”, in that case I can rename it to yuan’s-setup-wizard or something.
>
> I don’t know how useful could it be, since nowadays every body (understandably) starts with some community distribution rather than vanilla Emacs, but surely it is better than not having a wizard.
>
> You can try it out with emacs -q -l setup-wizard.el -f setup-wizard
I didn't yet try the package, but IMNSHO it makes the most sense in
core, and in that case it should also be started automatically for new
users, or at least suggested to them upon first invocation.
Thanks.
next prev parent reply other threads:[~2022-01-02 7:55 UTC|newest]
Thread overview: 119+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 2:07 Propose to add setup-wizard.el to ELPA 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-02 18:51 ` FW: [External] : " Drew Adams
2022-01-02 19:07 ` xenodasein--- via Emacs development discussions.
2022-01-02 21:29 ` Drew Adams
2022-01-02 22:14 ` Stefan Kangas
2022-01-03 6:42 ` Sean Whitton
2022-01-03 7:02 ` Stefan Kangas
2022-01-03 8:19 ` xenodasein--- via Emacs development discussions.
2022-01-03 9:27 ` Po Lu
2022-01-03 9:55 ` xenodasein--- via Emacs development discussions.
2022-01-03 10:10 ` Po Lu
2022-01-03 10:21 ` xenodasein--- via Emacs development discussions.
2022-01-03 10:53 ` Po Lu
2022-01-03 11:07 ` xenodasein--- via Emacs development discussions.
2022-01-03 11:25 ` Po Lu
2022-01-03 11:32 ` xenodasein--- via Emacs development discussions.
2022-01-03 12:13 ` Po Lu
2022-01-03 12:20 ` xenodasein--- via Emacs development discussions.
2022-01-03 12:32 ` Po Lu
2022-01-03 12:44 ` xenodasein--- via Emacs development discussions.
2022-01-03 12:55 ` Po Lu
2022-01-03 13:24 ` xenodasein--- via Emacs development discussions.
2022-01-03 15:15 ` xenodasein--- via Emacs development discussions.
2022-01-03 16:04 ` Drew Adams
2022-01-04 21:19 ` Sean Whitton
2022-01-04 21:28 ` Drew Adams
2022-01-04 22:38 ` Sean Whitton
2022-01-04 22:51 ` Drew Adams
2022-01-05 5:28 ` tomas
2022-01-05 7:43 ` Drew Adams
2022-01-05 8:13 ` tomas
2022-01-07 10:34 ` Jean Louis
2022-01-03 16:03 ` Drew Adams
2022-01-03 16:05 ` Stefan Monnier
2022-01-04 1:50 ` Yuan Fu
2022-01-04 2:53 ` Po Lu
2022-01-04 4:13 ` Stefan Monnier
2022-01-04 4:30 ` Yuan Fu
2022-01-04 6:10 ` Stefan Monnier
2022-01-04 15:04 ` Lars Ingebrigtsen
2022-01-04 21:25 ` Sean Whitton
2022-01-05 0:58 ` Po Lu
2022-01-05 15:35 ` Lars Ingebrigtsen
2022-01-06 6:32 ` Sean Whitton
2022-01-03 0:42 ` Po Lu
2022-01-02 18:47 ` [External] : " Drew Adams
2022-01-02 11:58 ` Philip Kaludercic
2022-01-07 10:09 ` Jean Louis
2022-01-02 18:47 ` [External] : " Drew Adams
2022-01-02 9:41 ` Po Lu
2022-01-02 17:18 ` Yuan Fu
2022-01-02 18:47 ` [External] : " Drew Adams
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 15:45 ` [External] : " Drew Adams
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2022-01-02 15:46 Simon Pugnet
2022-01-02 17:26 Simon Pugnet
2022-01-02 18:49 ` Stefan Kangas
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=83mtkeefmt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=emacs-devel@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).