From: "Daniel Martín" <mardani29@yahoo.es>
To: Jim Porter <jporterbugs@gmail.com>
Cc: Joost Kremers <joostkremers@fastmail.fm>,
Simon Pugnet <simon@polaris64.net>,
Stefan Kangas <stefan@marxist.se>,
emacs-devel@gnu.org
Subject: Re: Could Emacs Have a Set-up Wizard?
Date: Sat, 04 Sep 2021 11:34:42 +0200 [thread overview]
Message-ID: <m135qky98t.fsf@yahoo.es> (raw)
In-Reply-To: <62bfe109-1126-8d5f-ce84-bd9fe4ae1a71@gmail.com> (Jim Porter's message of "Fri, 3 Sep 2021 16:15:18 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
>
> Furthermore, a wizard could be useful for upgrading Emacs. Whether a
> new behavior is opt-in or opt-out, there are bound to be some that are
> so significant that it makes sense to notify the user. However, this
> would need some careful thought about how to be both 1) non-annoying
> and 2) maintainable. Making it much harder to add a significant new
> feature would be a bad move.
There's already a command in Emacs for that: M-x customize-changed first
asks for a version of Emacs (defaults to the previous one) and then
shows you every customization group, user option or face that is new or
its default has changed. So I think the wizard could reuse this command
or simply advertise it.
next prev parent reply other threads:[~2021-09-04 9:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 15:29 Gitlab Migration Simon Pugnet
2021-09-03 16:59 ` Could Emacs Have a Set-up Wizard? Stefan Kangas
2021-09-03 17:09 ` Simon Pugnet
2021-09-03 19:35 ` Joost Kremers
2021-09-03 23:15 ` Jim Porter
2021-09-04 9:34 ` Daniel Martín [this message]
2021-09-04 13:16 ` Simon Pugnet
2021-09-05 3:44 ` Richard Stallman
2021-09-04 3:27 ` Stefan Kangas
2021-09-04 13:25 ` Simon Pugnet
2021-09-04 14:21 ` Daniel Fleischer
2021-09-04 15:33 ` Simon Pugnet
2021-09-04 16:44 ` Yuan Fu
2021-09-04 17:06 ` Simon Pugnet
2021-09-05 4:34 ` Arthur Miller
-- strict thread matches above, loose matches on Subject: below --
2021-09-04 14:53 Simon Pugnet
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=m135qky98t.fsf@yahoo.es \
--to=mardani29@yahoo.es \
--cc=emacs-devel@gnu.org \
--cc=joostkremers@fastmail.fm \
--cc=jporterbugs@gmail.com \
--cc=simon@polaris64.net \
--cc=stefan@marxist.se \
/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).