From: Daniel Fleischer <danflscr@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: [External] : Re: [PATCH] Package Installation in Tutorial
Date: Fri, 03 Dec 2021 19:48:20 +0200 [thread overview]
Message-ID: <m2zgph4m1n.fsf@gmail.com> (raw)
In-Reply-To: SJ0PR10MB5488D70FD258ECCD01E87EFAF36A9@SJ0PR10MB5488.namprd10.prod.outlook.com
Hi Drew, interesting points.
> Is using the Customize UI in the tutorial?
> Is making simple customizations with Lisp
> in the tutorial? Is use of `custom-file'
> in the tutorial? Is use of the `Options'
> menu in the tutorial?
It's sounds like whataboutism. If you think there are glaring omissions
in topics to be introduced to new users, let's add them.
> Is `load-path', `require', or `load-library'
> introduced in the tutorial?
Based on my experience with competing editors (sorry for reducing Emacs
to being an editor) when first starting up the topics of selecting a
theme and installing packages are presented first. After that, some
customization is offered.
> How many nowadays _are_ aware of that "main
> feature" but are unaware of how to find and
> change a face or option value? How many are
> unaware of how to _ask Emacs_, to find out
> for themselves about such things?
That's a trick question due to selection bias. Emacs is not easy to
learn; if you poll existing users, they probably figured out how to
install packages. We're talking about first timers, people that make
their first steps in Emacs. When these people get stuck, the no. 1
comment they receive is "do the tutorial". That's where we need to
present the Emacs ontology: windows, frames, undo/redo, modeline,
help-searching and also package management which is the least alien part
in Emacs.
> The whole discussion (by 3 people) of this
> change has been only about _where_ to add
> this topic - nothing about why to do so,
> or what other changes might be just as
> important or more so.
Do you want to open up a discussion about how the tutorial is build, or
how to make Emacs easier for new users? great, but let's start with
something.
> Has it been shown that new users _are_ in
> general unaware of packages or unable to
> install them? Aside from questions about
> an early init file or `use-package' syntax
> etc., how many new users just ask "How do
> I install a package?" I don't see that
> come up, myself, on Reddit, StackExchange,
> help-gnu-emacs, etc., and I come across
> dozens (hundreds?), of new-user questions
> every day.
Fair point. Does it mean we shouldn't try to anticipate pain points for,
say, new users, and introduce features we think may help them, unless
new users explicitly complain of lack of such features?
> A good indication of such a need might be
> the number of existing blogs, videos, etc.
> telling users how to install and delete a
> package - and how much they're used. Do
> we have an impression (or tally) of this?
> Is there a crying lack of such help?
When did any change been introduced to Emacs due to some contributor
seeing blog posts mentioning such and such aspects of Emacs being
problematic/hard to configure/missing a feature?
--
Daniel Fleischer
next prev parent reply other threads:[~2021-12-03 17:48 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 17:30 [PATCH] Package Installation in Tutorial Daniel Fleischer
2021-12-01 18:06 ` Daniel Martín
2021-12-01 19:25 ` Stefan Kangas
2021-12-01 19:25 ` Stefan Kangas
2021-12-02 6:42 ` Daniel Fleischer
2021-12-02 9:09 ` Juri Linkov
2021-12-02 11:17 ` Stefan Kangas
2021-12-03 6:57 ` Daniel Fleischer
2021-12-03 16:29 ` [External] : " Drew Adams
2021-12-03 17:48 ` Daniel Fleischer [this message]
2021-12-03 18:53 ` Stefan Kangas
2021-12-03 18:56 ` Drew Adams
2021-12-03 18:53 ` Drew Adams
2021-12-03 19:24 ` Stefan Kangas
2021-12-03 20:24 ` Drew Adams
2021-12-03 22:54 ` Stefan Kangas
2021-12-03 21:19 ` Daniel Fleischer
2021-12-03 23:01 ` Drew Adams
2021-12-04 8:06 ` Eli Zaretskii
2021-12-04 11:04 ` Daniel Fleischer
2021-12-04 18:16 ` Drew Adams
2021-12-04 21:06 ` Daniel Fleischer
2021-12-04 17:38 ` Drew Adams
2021-12-04 5:44 ` Richard Stallman
2021-12-04 8:04 ` Eli Zaretskii
2021-12-04 17:20 ` Drew Adams
2021-12-04 17:18 ` Drew Adams
2021-12-03 17:00 ` Lars Ingebrigtsen
2021-12-04 13:08 ` Stefan Kangas
2021-12-04 14:15 ` Daniel Fleischer
2021-12-04 16:29 ` Eli Zaretskii
2021-12-04 20:38 ` Daniel Fleischer
2021-12-04 21:58 ` Lars Ingebrigtsen
2021-12-05 9:37 ` Daniel Fleischer
2021-12-05 20:52 ` Lars Ingebrigtsen
2021-12-05 10:21 ` Eli Zaretskii
2021-12-05 10:54 ` Daniel Fleischer
2021-12-05 11:44 ` Stefan Kangas
2021-12-05 15:33 ` Daniel Fleischer
2021-12-06 10:36 ` Daniel Fleischer
2021-12-06 14:10 ` Stefan Kangas
2021-12-05 11:29 ` 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=m2zgph4m1n.fsf@gmail.com \
--to=danflscr@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).