unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Describe keymap
Date: Mon, 14 Dec 2020 03:33:27 +0100	[thread overview]
Message-ID: <87im95yv48.fsf@web.de> (raw)
In-Reply-To: 874kkpzcoa.fsf@zoho.eu

Emanuel Berg via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:

>   S <t>           gnus-article-read-summary-send-keys

That is actually `t', the symbol, and
(info "(elisp) Format of Keymaps") tells you:

| ‘(t . BINDING)’
|      This specifies a “default key binding”; any event not bound by
|      other elements of the keymap is given BINDING as its binding.
|      Default bindings allow a keymap to bind all possible event types
|      without having to enumerate all of them.  A keymap that has a
|      default binding completely masks any lower-precedence keymap,
|      except for events explicitly bound to ‘nil’ (see below).

In this special case, S lets you invoke summary buffer commands from
within the article buffer.  Try e.g. S f with the article buffer
current.

> the angle brackets; and
>
>   <remap>         Prefix Command
>   <remap> <self-insert-command>   gnus-article-read-summary-keys

Again, these are symbols.  The items are command remappings, and this is
explained in (info "(elisp) Remapping Commands").

Seems the brackets just denote symbols, ordinary keys most of the time,
like <f1>, compared to keys that are numbers internally, like "k".

Michael.




  parent reply	other threads:[~2020-12-14  2:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201213195427.jyn4vwkayqujbnwh.ref@Ergus>
2020-12-13 19:54 ` Describe keymap Ergus
2020-12-13 20:01   ` Drew Adams
2020-12-13 20:14     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-13 23:18       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14  1:31         ` FW: " Drew Adams
2020-12-14  2:38           ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14  8:46             ` Robert Pluim
2020-12-14  9:01               ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14  9:57                 ` Robert Pluim
2020-12-14 10:05                   ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-12-14 10:30                     ` Robert Pluim
2020-12-14 13:27                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 17:08                       ` Robert Pluim
2020-12-14 18:23                         ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-15 10:18                           ` Robert Pluim
2020-12-15 20:41                             ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 13:23                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14  1:31       ` Drew Adams
2020-12-14  2:33       ` Michael Heerdegen [this message]
2020-12-14  2:40         ` Emanuel Berg via Users list for the GNU Emacs text editor

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=87im95yv48.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=help-gnu-emacs@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.
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).