From: Eli Zaretskii <eliz@gnu.org>
To: Summer Emacs <summeremacs@summerstar.me>
Cc: corwin@bru.st, emacs-devel@gnu.org
Subject: Re: Emacs Newbie Info Pages
Date: Fri, 13 Sep 2024 13:46:00 +0300 [thread overview]
Message-ID: <86plp7kf13.fsf@gnu.org> (raw)
In-Reply-To: <51D1701A-4E38-4D8F-9D9C-ABDD7013933E@summerstar.me> (message from Summer Emacs on Fri, 13 Sep 2024 09:45:25 +0200)
> From: Summer Emacs <summeremacs@summerstar.me>
> Date: Fri, 13 Sep 2024 09:45:25 +0200
> Cc: Corwin Brust <corwin@bru.st>,
> emacs-devel@gnu.org
>
> > On Sep 13, 2024, at 08:38, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> >> From: Corwin Brust <corwin@bru.st>
> >> Date: Thu, 12 Sep 2024 13:29:40 -0500
> >> Cc: emacs-devel@gnu.org
> >>
> >> Would it make sense to have a `emacs-welcome-new-user' mode which
> >> "collects" configuration defaults appropriate for new users and
> >> provides means to enable (and, perhaps, disable) them en masse?
> >
> > This was discussed in the past (search the archives), but never went
> > anywhere beyond the discussion. The idea is certainly sensible, but
> > implementing it is a challenge, since different groups of users/usage
> > patterns need different stuff in such a mode.
>
> Yeah. I’ve been told. The problem with this is the following:
>
> Premise: Everyone is different. Everyone has different needs.
>
> Deduction: No tutorial will ever meet the needs of every single person.
>
> Conclusion: Let’s not do anything.
>
> Instead, let’s try this:
>
> Premise: Most people who use Emacs are devs.
> Given: Not everyone who uses Emacs is a dev.
> Deduction: The people who aren’t devs may get lost in the assumptions made in Emacs welcome pages.
> Conclusion: Let’s make a tutorial for people who aren’t devs.
>
> I think mine sounds better and, maybe with a little luck and a touch of effort, we may get somewhere. =)
I think the "conclusion" you cite above, to do nothing, is not a
conclusion we arrived at. (I also think it's a bit unfair to claim
that we arrived at such a "conclusion": it almost says we make silly
conclusions here.) I think instead we acknowledged the problem and
tried to find solutions for it, like trying to identify the meaningful
classes/groups of users, so as to have a dedicated tutorial/mode for
each one of them.
I think a tutorial for people who are not software developers is an
okay solution, but that doesn't make the issue go away: non-developers
are still not a homogeneous group, and the challenge I mentions still
exists, albeit is perhaps smaller.
next prev parent reply other threads:[~2024-09-13 10:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 17:30 Emacs Newbie Info Pages Summer Emacs
2024-09-12 18:26 ` Philip Kaludercic
2024-09-12 18:45 ` Summer Emacs
2024-09-12 19:17 ` Philip Kaludercic
2024-09-13 6:40 ` Eli Zaretskii
2024-09-13 7:36 ` Philip Kaludercic
2024-09-13 7:39 ` Summer Emacs
2024-09-13 14:46 ` Juergen Fenn
2024-09-13 12:28 ` Thanos Apollo
2024-09-12 18:29 ` Corwin Brust
2024-09-12 19:00 ` Summer Emacs
2024-09-13 2:24 ` Suhail Singh
2024-09-17 3:47 ` Richard Stallman
2024-09-17 10:58 ` Summer Emacs
2024-09-17 13:31 ` Eli Zaretskii
2024-09-17 14:12 ` Summer Emacs
2024-09-17 14:48 ` Emanuel Berg
2024-09-17 16:45 ` Summer Emacs
2024-09-18 1:09 ` Emanuel Berg
2024-09-17 15:44 ` Eli Zaretskii
2024-09-17 16:49 ` Summer Emacs
2024-09-17 17:53 ` Eli Zaretskii
2024-09-19 3:51 ` Richard Stallman
2024-09-19 9:45 ` Summer Emacs
2024-09-13 6:38 ` Eli Zaretskii
2024-09-13 7:45 ` Summer Emacs
2024-09-13 10:46 ` Eli Zaretskii [this message]
2024-09-13 11:20 ` Summer Emacs
2024-09-13 11:57 ` Eli Zaretskii
2024-09-13 12:09 ` Summer Emacs
2024-09-13 13:31 ` Eli Zaretskii
2024-09-18 8:13 ` Emanuel Berg
2024-09-18 20:02 ` Juergen Fenn
2024-09-20 2:39 ` Emanuel Berg
2024-09-22 12:37 ` Peter Oliver
2024-09-22 14:31 ` Eli Zaretskii
2024-09-13 6:35 ` Eli Zaretskii
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=86plp7kf13.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=corwin@bru.st \
--cc=emacs-devel@gnu.org \
--cc=summeremacs@summerstar.me \
/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).