unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Joost Kremers <joostkremers@fastmail.fm>,
	Simon Pugnet <simon@polaris64.net>
Cc: Stefan Kangas <stefan@marxist.se>, emacs-devel@gnu.org
Subject: Re: Could Emacs Have a Set-up Wizard?
Date: Fri, 3 Sep 2021 16:15:18 -0700	[thread overview]
Message-ID: <62bfe109-1126-8d5f-ce84-bd9fe4ae1a71@gmail.com> (raw)
In-Reply-To: <871r65peql.fsf@fastmail.fm>

On 9/3/2021 12:35 PM, Joost Kremers wrote:
> I also think it's a good idea, but I don't think it's entirely orthogonal to the
> idea of profiles. I don't really see how profiles would make it easier for new
> users to start using Emacs. A wizard, on the other hand, seems to me to be much
> better suited for that purpose. (If done right, of course.)

I agree. While profiles improve upon the current state of affairs in 
some ways, a wizard would (theoretically) make it easier for a user to 
set up a starting configuration that makes sense for them. Rather than 
picking between one of a handful of profiles, the user could 
mix-and-match as needed. Done well, it could even give users a glimpse 
into how to hand-edit their .emacs when they're ready to start 
more-elaborate customization.

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.

> In fact, I would even suggest having the wizard run automatically if no init
> file is found (with a button to quit the wizard, of course).

Also agreed (with the caveat that `emacs -Q' shouldn't start the 
wizard). In my experience, Emacs does a great job of guiding the 
moderately-experienced user, but there's an awful lot to get used to a 
brand-new user. Having something that helps get past the first hurdle of 
setting up the basics would go a long way, I think.

In fact, I bounced off Emacs the first couple times I tried it, and 
might not have picked it up at all if it hadn't been the only option I 
had for a time (other than vim, which I had an even harder time getting 
started with). Surely there are plenty of people out there who bounced 
off and never returned.

- Jim



  reply	other threads:[~2021-09-03 23:15 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 [this message]
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
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=62bfe109-1126-8d5f-ce84-bd9fe4ae1a71@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=joostkremers@fastmail.fm \
    --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).