[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU Emacs raison d'etre
From: |
Karl Fogel |
Subject: |
Re: GNU Emacs raison d'etre |
Date: |
Wed, 27 May 2020 23:12:22 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
On 14 May 2020, Richard Stallman wrote:
>>Another area is the keybinding space and the minibuffer. Just
>>about every time I have watched a new user use Emacs, I have noticed
>>how frequently they accidentally hit some key combination or sequence
>>and wind up in some weird state that they never meant to be in -- and
>>don't know how to get out of.
>
>We made this very simple a few years ago: Just keep typing C-g.
>I guess these users don't know that.
Sometimes they know that, but it's still stressful for them to have to do it.
They don't like the sensation of getting into state they don't understand, and
then having to type a magical quit-key to get out of that state. It makes them
apprehensive about even using the editor -- they feel like they got bitten.
>Can anyone thing of a better way to teach them about this?
>It could teach them first about the minibuffer, then about C-g
>to get out. It could copy the current minibuffer prompt
>into the help screen to make the explanation clearer.
>
>The tricky part is how to detect when a user could use this help.
I don't think the issue is ignorance about C-g. It's that people have a
relationship with software interfaces in which they're not accustomed to being
bitten. Even when the bite draws no blood, they still don't like the feeling.
I can see directly that they don't like the feeling, that it's upsetting to
them. I conjecture that part of the reason is that even if they quickly
ascertain that everything's all right this time, they still have a (rational)
fear that the next time the bite might actually cause harm -- e.g., that maybe
they'll lose a file, or accidentally rename something, or that edits that they
don't know about will be accidentally made somewhere.
I haven't actually asked new users if that's their worry, but on the now-rare
occasions when Emacs bites me, I worry about such things. Also, I've been
using Emacs long enough to know that most likely nothing harmful happened, and
that if I patiently unwind the state I'll be able to figure it all out. A
newcomer does not have that comfort at first, and they can only acquire it
through sustained exposure to the editor.
Again, none of the above is meant to suggest that Emacs should change
something. I'm just saying that we should be intentional about the kinds of
users Emacs is likely to attract, and not make changes designed around people
who are unlikely to be long-term Emacs users anyway.
Best regards,
-Karl
- Re: GNU Emacs raison d'etre, (continued)
- Re: GNU Emacs raison d'etre, Dmitry Gutov, 2020/05/18
- RE: GNU Emacs raison d'etre, Drew Adams, 2020/05/17
- RE: GNU Emacs raison d'etre, Drew Adams, 2020/05/17
- RE: GNU Emacs raison d'etre, Drew Adams, 2020/05/17
- Re: GNU Emacs raison d'etre, Dmitry Gutov, 2020/05/17
- Re: GNU Emacs raison d'etre, Sergey Organov, 2020/05/17
- Re: GNU Emacs raison d'etre, Dmitry Gutov, 2020/05/17
- RE: GNU Emacs raison d'etre, Drew Adams, 2020/05/17
- Re: GNU Emacs raison d'etre, Arthur Miller, 2020/05/16
- Re: GNU Emacs raison d'etre, Richard Stallman, 2020/05/16
- Re: GNU Emacs raison d'etre,
Karl Fogel <=
- Re: GNU Emacs raison d'etre, Eduardo Ochs, 2020/05/28
- RE: GNU Emacs raison d'etre, Drew Adams, 2020/05/28
- RE: GNU Emacs raison d'etre, excalamus, 2020/05/28
- Re: GNU Emacs raison d'etre, Jean-Christophe Helary, 2020/05/28
- RE: GNU Emacs raison d'etre, Drew Adams, 2020/05/28
- Re: GNU Emacs raison d'etre, Jean-Christophe Helary, 2020/05/29
- Re: GNU Emacs raison d'etre, Philip K., 2020/05/28
- Re: GNU Emacs raison d'etre, João Távora, 2020/05/28
- Re: GNU Emacs raison d'etre, T.V Raman, 2020/05/28
- Message not available
- Re: GNU Emacs raison d'etre, excalamus, 2020/05/28