unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Pugnet <simon@polaris64.net>
To: Stefan Kangas <stefan@marxist.se>
Cc: Joost Kremers <joostkremers@fastmail.fm>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Could Emacs Have a Set-up Wizard?
Date: Sat, 04 Sep 2021 13:25:35 +0000	[thread overview]
Message-ID: <878s0cjwvs.fsf@polaris64.net> (raw)
In-Reply-To: <CADwFkmkVkt+aatihmskmvPRrPqmV_q+K=Accib-NJ_umFbAong@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]

Stefan Kangas <stefan@marxist.se> writes:

>> A wizard, on the other hand, presents a new user with a couple of choices, each
>> of which can be explained on the spot and the necessary change to the init file
>> made visible. Add a comment to each change with the same explanation that
>> appears in the wizard and the new user can easily see how to undo the change if
>> they end up not liking it.
>
> If we could do it well, that sounds like it could be a good idea.
> Maybe we could let the user choose such a mode of operation
> optionally, while hiding the nitty-gritty details by default.

I think it's important to expose the user to the nitty-gritty to some
extent. I envisage the wizard as being a first step into learning Emacs,
so while it hides the details of how it generates a configuration based
on the user's choices it will show the generated code in the end. It
could display the init.el buffer after the wizard is complete and then
show exactly where this file is saved.

As I think was mentioned in this thread earlier too, adding helpful
comments above each generated section of configuration would be very
important. The goal I think would be to encourage users to fiddle and
experiment, but also to allow them to get started right away without
having to understand things first.

Give someone a configuration and they'll be enlightened for a month,
teach them how to build their own configuration and they'll be
enlightened for life :)

[-- Attachment #2: attachment.sig --]
[-- Type: application/pgp-signature, Size: 877 bytes --]

  reply	other threads:[~2021-09-04 13:25 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
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 [this message]
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=878s0cjwvs.fsf@polaris64.net \
    --to=simon@polaris64.net \
    --cc=emacs-devel@gnu.org \
    --cc=joostkremers@fastmail.fm \
    --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).