all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marco Wahl <marcowahlsoft@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Kangas <stefan@marxist.se>,
	larsi@gnus.org, 50727@debbugs.gnu.org, marcowahlsoft@gmail.com
Subject: bug#50727: Contradictory conventions with new command kbd-macro-display
Date: Wed, 22 Sep 2021 09:01:53 +0200	[thread overview]
Message-ID: <87lf3pum8u.fsf@gmail.com> (raw)
In-Reply-To: <83tuidw2wc.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 22 Sep 2021 09:16:51 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Stefan Kangas <stefan@marxist.se>
>> Date: Tue, 21 Sep 2021 16:22:26 -0700
>> Cc: larsi@gnus.org, marcowahlsoft@gmail.com
>>
>>     The key sequences [C-x C-k 0] through [C-x C-k 9] and [C-x C-k A]
>>     through [C-x C-k Z] are reserved for user bindings, and to bind to
>>     one of these sequences, just enter the digit or letter, rather than
>>     the whole sequence.
>
> Regardless of the main issue here, why does this doc string use this
> strange notation for key sequences?  What is the meaning of the
> brackets here, and why don't we use `..' as usual?

Of course I don't know but I guess the reason for that notation has been
just a lack of knowledge about the usual notation style.






      parent reply	other threads:[~2021-09-22  7:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21 23:22 bug#50727: Contradictory conventions with new command kbd-macro-display Stefan Kangas
2021-09-21 23:27 ` Gregory Heytings
2021-09-22  6:37   ` Stefan Kangas
2021-09-22  6:58     ` Marco Wahl
2021-09-22 19:57       ` Lars Ingebrigtsen
2021-09-22  7:01     ` Gregory Heytings
2021-09-22  6:16 ` Eli Zaretskii
2021-09-22  6:53   ` Stefan Kangas
2021-09-22  7:34     ` Eli Zaretskii
2021-09-22  7:01   ` Marco Wahl [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lf3pum8u.fsf@gmail.com \
    --to=marcowahlsoft@gmail.com \
    --cc=50727@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=stefan@marxist.se \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.