From: Lars Ingebrigtsen <larsi@gnus.org>
To: Josh <josh@foxtail.org>
Cc: jrm@ftfl.ca, Glenn Morris <rgm@gnu.org>, 12976@debbugs.gnu.org
Subject: bug#12976: 24.2; C-c i is bound to custom function, but in a term buffer it gets bound to ido-insert-file
Date: Sat, 04 Dec 2021 05:31:19 +0100 [thread overview]
Message-ID: <87zgphouso.fsf@gnus.org> (raw)
In-Reply-To: <CANdFEAFYd-6Y=9sSuO1aube6X87TDk+tNgrJbbUoHc1H-+yi+g@mail.gmail.com> (josh@foxtail.org's message of "Sat, 13 Jul 2013 18:14:20 -0700")
Josh <josh@foxtail.org> writes:
>> I consider this not a bug.
>
> I certainly do. From (info "(elisp) Key Binding Conventions") :
>
> * Don't define `C-c LETTER' as a key in Lisp programs. Sequences
> consisting of `C-c' and a letter (either upper or lower case) are
> reserved for users; they are the *only* sequences reserved for
> users, so do not block them.
[...]
> The passage I cited refers to "all the Emacs major modes". Is there
> any reason to believe that term.el should be exempt from adhering to
> this convention?
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
It's an oddball mode, and it breaks many Emacs conventions. In any
case, this isn't something we can change at this point, since the `C-c'
key bindings are ingrained at this point. (You can change
`term-escape-char' if you want, though.)
So I'm reclosing this bug report as a WONTFIX.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-12-04 4:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 0:32 bug#12976: 24.2; C-c i is bound to custom function, but in a term buffer it gets bound to ido-insert-file Joseph Mingrone
2012-11-24 3:43 ` Glenn Morris
2013-07-12 1:52 ` Leo Liu
2013-07-14 1:14 ` Josh
2021-12-04 4:31 ` Lars Ingebrigtsen [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
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=87zgphouso.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=12976@debbugs.gnu.org \
--cc=josh@foxtail.org \
--cc=jrm@ftfl.ca \
--cc=rgm@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.
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).