From: Lars Ingebrigtsen <larsi@gnus.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: Moving image commands to one submap
Date: Sat, 24 Sep 2022 11:29:23 +0200 [thread overview]
Message-ID: <87leq915os.fsf@gnus.org> (raw)
In-Reply-To: <87zgeqc7pq.fsf@gmail.com> (Augusto Stoffel's message of "Fri, 23 Sep 2022 19:37:53 +0200")
Augusto Stoffel <arstoffel@gmail.com> writes:
>> C-c C-i C-m C-a C-g C-e ?
>>
>> Stefan "always happy to help"
Thanks, thanks.
> This seems to be a more general question than just image commands.
> There should be a prefix available for all keymaps which are used as a
> text property and want to be polite, I think.
>
> How about “C-x .”, “C-c .” or something like that?
It's a bit awkward to type `C-x . +' for instance...
> PS: I put the Python import commands under “C-c C-i”, which, among
> potential issues, display as “C-c TAB” on the menus. So if someone
> finds that bad, please complain in due time.
Our long term plan is to try to fix this issue (so that things show up
as intended for `C-i' and `C-m') -- there's several ideas, but nobody's
gone ahead and done it yet. So I think it's fine to use `C-c C-i' even
if it's currently a bit wonky.
next prev parent reply other threads:[~2022-09-24 9:29 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 [this message]
2022-09-24 18:36 ` Juri Linkov
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
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=87leq915os.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=arstoffel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).