unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Tatsu Takamaro <tatsu.takamaro@gmail.com>
Cc: Drew Adams <drew.adams@oracle.com>,
	 "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: [External] : Q1 - the keys' bindings to work more widely
Date: Tue, 17 Dec 2024 13:28:18 +0700	[thread overview]
Message-ID: <CAP_d_8Vtp_afE-VoVahYBx+OMS2vvt=6rahj+di-KXF17AD1jg@mail.gmail.com> (raw)
In-Reply-To: <03456761-0989-478b-2b77-593142693ca7@gmail.com>

On Tue, 17 Dec 2024 at 12:42, Tatsu Takamaro <tatsu.takamaro@gmail.com> wrote:

> This one works:
>
>     *:keymap '(keymap (?a . kill-ring-save)))*
>
> But I'm not sure why.

You’re not actually supposed to type out keymaps in their internal
representation. Drew probably does that because he learned Emacs
before the introduction of key binding helper functions.

    (defvar ttkeys-mode-map
      (define-keymap
         "C-c" #'kill-ring-save
         "C-a" #'mark-whole-buffer))

    (define-minor-mode ttkeys-mode "Regular key bindings"
      :init-value t
      :lighter " TT"
      :global t
      :keymap ttkeys-mode-map)

(I must note that you’re in for a lot of swimming against the current
if you want to reclaim C-c from its established Emacs role as a
prefix. A lot of modes bind some of their functionality to sequences
starting with C-c, and you will either have to rebind them in order to
start using them, or they will wrest C-c back from you.)



  reply	other threads:[~2024-12-17  6:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-14 23:46 Q1 - the keys' bindings to work more widely Tatsu Takamaro
2024-12-15  2:15 ` [External] : " Drew Adams
2024-12-16 23:11   ` Tatsu Takamaro
2024-12-16 23:55     ` Drew Adams via Users list for the GNU Emacs text editor
2024-12-17  0:05       ` Drew Adams
2024-12-17  0:16         ` Tatsu Takamaro
2024-12-17  2:17           ` Drew Adams
2024-12-17  5:41             ` Tatsu Takamaro
2024-12-17  6:28               ` Yuri Khan [this message]
2024-12-17  5:42             ` Tatsu Takamaro
2024-12-15 10:05 ` Alain.Cochard

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='CAP_d_8Vtp_afE-VoVahYBx+OMS2vvt=6rahj+di-KXF17AD1jg@mail.gmail.com' \
    --to=yuri.v.khan@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tatsu.takamaro@gmail.com \
    /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).