unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
	Andrew Goh <andrewgoh95@yahoo.com.sg>,
	41403@debbugs.gnu.org
Subject: bug#41403: A more user-friendly version of GNU Emacs
Date: Fri, 17 Sep 2021 13:57:33 -0700	[thread overview]
Message-ID: <CADwFkmmhE9rD8XUyy-djNg-pAKwUSZQrxQ5hjUoxjGOTpTGV7A@mail.gmail.com> (raw)
In-Reply-To: <87zgsbtaqr.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

>>> I guess, the key, M-x.  The refcard assumes that people know what it
>>> (meta) is.  It would probably good to explain it.
>>
>> Right, okay.  If that's it, I agree that it should probably be added.
>>
>> If we do that, we might as well explain that "C-" stands for "Ctrl" and
>> "S-" stands for "Shift" while we're at it.  (If there's enough space.)
>
> I don't think the refcard is the place to explain these keys -- the
> refcard is for quick lookup when you know the basics.
>
> The tutorial explains all this stuff, and that's the correct place, so
> I'm closing this bug report.

I took a look at the refcards, and it is pretty full of stuff already.

One thing caught my eye, namely this information:

    Starting Emacs
    To enter GNU Emacs 28, just type its name: emacs

This seems useless, for two reasons:
A) The overwhelming majority of users will click an icon to start Emacs.
B) Any other users will already know to type "emacs".

This leaves me wondering if putting a brief explanation of our strange
key conventions on there isn't a better use of space.





  reply	other threads:[~2021-09-17 20:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1572340523.1158427.1589893725280.ref@mail.yahoo.com>
2020-05-19 13:08 ` bug#41403: A more user-friendly version of GNU Emacs Andrew Goh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-19 14:43   ` Stefan Kangas
2020-05-19 22:48     ` Michael Heerdegen
2020-05-19 23:02       ` Stefan Kangas
2021-09-17 16:42         ` Lars Ingebrigtsen
2021-09-17 20:57           ` Stefan Kangas [this message]
2021-09-17 22:04             ` Michael Heerdegen
2021-09-18 13:33             ` Lars Ingebrigtsen
2021-09-21 20:13               ` Stefan Kangas
2021-09-21 20:14                 ` Lars Ingebrigtsen
2021-09-21 23:07                   ` Stefan Kangas
2021-09-21 23:22                     ` Lars Ingebrigtsen
2021-09-22  0:30                       ` Michael Heerdegen
2021-09-22 21:24                         ` Richard Stallman
2021-09-22 21:34                           ` Lars Ingebrigtsen
2021-09-23  6:24                             ` Eli Zaretskii
2021-09-22 14:41                       ` Stefan Kangas
2021-09-22 15:57                         ` Andreas Schwab
2021-09-22 20:00                         ` Lars Ingebrigtsen
2021-09-22 22:28                           ` Stefan Kangas
2021-09-22 21:42                         ` Alan Third
2021-09-22 22:28                           ` Stefan Kangas
     [not found]     ` <1269710845.1235081.1589931944379@mail.yahoo.com>
2020-05-20  0:55       ` Stefan Kangas
     [not found]         ` <919459122.1576791.1589981239406@mail.yahoo.com>
2020-05-20 13:37           ` Stefan Kangas
2021-09-17 18:44   ` Eduardo Ochs
     [not found] <DE284271-933A-4DB1-9D01-2E21F43E6201@acm.org>
2021-09-22 18:01 ` Andreas Schwab
2021-09-22 18:47   ` Mattias Engdegård

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=CADwFkmmhE9rD8XUyy-djNg-pAKwUSZQrxQ5hjUoxjGOTpTGV7A@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=41403@debbugs.gnu.org \
    --cc=andrewgoh95@yahoo.com.sg \
    --cc=larsi@gnus.org \
    --cc=michael_heerdegen@web.de \
    /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).