From: Yuan Fu <casouri@gmail.com>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Gather a list of confusions beginner tend to have
Date: Tue, 8 Sep 2020 13:28:18 -0400 [thread overview]
Message-ID: <6936F2AB-0968-42B5-9914-56538608A42C@gmail.com> (raw)
I think everybody would agree on attracting more people to use Emacs—that means more blogs and help, more contributor, etc. And people agree that Emacs isn’t as beginner-friendly as it could be. The problem is what to improve, and how.
As the first step, we should collect real experiences from real beginners: someone starts to use Emacs just recently (e.g., less than one year). Ask people around, ask people on the internet. I’ll post on reddit for some input. Can I use a title like “Emacs developers wants to know what confuses beginners in vanilla Emacs?”
Once we have an idea on what real beginners are complaining about, we can then try to improve them.
Yuan
next reply other threads:[~2020-09-08 17:28 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 17:28 Yuan Fu [this message]
2020-09-10 11:51 ` Gather a list of confusions beginner tend to have Jean Louis
2020-09-10 12:51 ` tomas
2020-09-15 7:11 ` Andreas Röhler
2020-09-15 8:21 ` Robert Pluim
2020-09-15 10:13 ` Andreas Röhler
2020-09-15 10:34 ` Robert Pluim
2020-09-15 11:22 ` Göktuğ Kayaalp
-- strict thread matches above, loose matches on Subject: below --
2020-09-08 18:48 Göktuğ Kayaalp
2020-09-08 19:30 ` Yuan Fu
2020-09-08 21:30 ` Praharsh Suryadevara
2020-09-09 3:51 ` Richard Stallman
2020-09-09 14:18 ` Eli Zaretskii
2020-09-09 14:24 ` Göktuğ Kayaalp
2020-09-09 15:07 ` Stefan Kangas
2020-09-09 16:09 ` Göktuğ Kayaalp
2020-09-09 16:23 ` Praharsh Suryadevara
2020-09-09 16:06 ` Praharsh Suryadevara
2020-09-11 4:13 ` Richard Stallman
2020-09-11 4:13 ` Richard Stallman
2020-09-11 4:41 ` Praharsh Suryadevara
2020-09-09 7:57 ` tomas
2020-09-10 2:40 ` Richard Stallman
2020-09-10 3:32 ` Eli Zaretskii
2020-09-10 8:29 ` tomas
2020-09-10 9:08 ` Gregory Heytings via Emacs development discussions.
2020-09-10 9:34 ` Eli Zaretskii
2020-09-10 10:08 ` tomas
2020-09-10 9:30 ` Eli Zaretskii
2020-09-10 10:11 ` tomas
2020-09-11 4:18 ` Richard Stallman
2020-09-11 7:06 ` Eli Zaretskii
2020-09-11 13:47 ` Stefan Monnier
2020-09-12 3:22 ` Richard Stallman
2020-09-12 3:46 ` Emanuel Berg via Emacs development discussions.
2020-09-10 8:28 ` tomas
2020-09-09 14:01 ` Eli Zaretskii
2020-09-10 23:20 ` Yuan Fu
2020-09-11 6:45 ` Eli Zaretskii
2020-09-11 8:51 ` Dmitry Gutov
2020-09-11 8:59 ` Emanuel Berg via Emacs development discussions.
2020-09-11 13:52 ` Yuan Fu
2020-09-11 14:01 ` Eli Zaretskii
2020-09-11 14:27 ` Stefan Monnier
2020-09-09 2:01 ` Nick Savage
2020-09-09 14:48 ` Göktuğ Kayaalp
2020-09-10 2:36 ` Richard Stallman
2020-09-10 10:07 ` Göktuğ Kayaalp
2020-09-10 17:28 ` Drew Adams
2020-09-10 21:17 ` Göktuğ Kayaalp
2020-09-08 20:10 Göktuğ Kayaalp
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=6936F2AB-0968-42B5-9914-56538608A42C@gmail.com \
--to=casouri@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).