all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Moving image commands to one submap
Date: Sat, 24 Sep 2022 21:36:12 +0300	[thread overview]
Message-ID: <86v8pc7gab.fsf@mail.linkov.net> (raw)
In-Reply-To: <87zgeq3xuu.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 23 Sep 2022 17:38:01 +0200")

> When the image keymap was introduced, it only had a couple of commands,
> so triggering something by accident wasn't a major worry.  But it's now
> grown a large number of bindings, so people are hitting these commands
> more by accident.
>
> So I think we should move them all under one prefix, to make this less
> likely, and also then make the applicable commands use repeat-map.  For
> instance, `+ + +' would become `<something> + + +' etc (to increase the
> size of an image).
>
> But what should <something> be?  Something with "image" mnemonics and
> simple to type, but `C-i' isn't an option (because of confusion with
> `TAB').

I can't imagine a need to use self-inserting keys while point is on an image.
So why not just 'i' and then the image keymap with '+ - + - ...'
Or the same keymap directly without 'i'.



  parent reply	other threads:[~2022-09-24 18:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 15:38 Moving image commands to one submap Lars Ingebrigtsen
2022-09-23 15:56 ` Stefan Monnier
2022-09-23 17:37   ` Augusto Stoffel
2022-09-24  9:29     ` Lars Ingebrigtsen
2022-09-24 18:36 ` Juri Linkov [this message]
2022-09-24 19:09   ` Lars Ingebrigtsen
2022-09-24 19:54     ` Juri Linkov
2022-09-24 20:12       ` Lars Ingebrigtsen
2022-09-25  7:23         ` Juri Linkov
2022-09-25  9:58           ` Lars Ingebrigtsen
2022-09-24 22:33   ` Stefan Monnier
2022-09-25  9:52     ` Lars Ingebrigtsen
2022-10-04 13:10 ` Lars Ingebrigtsen

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=86v8pc7gab.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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.
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.