From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Custom keybinding getting over-ridden in python mode
Date: Sat, 5 Apr 2014 09:21:56 -0700 (PDT) [thread overview]
Message-ID: <d8ac2507-c9c8-4bf4-bc89-254d7137401a@googlegroups.com> (raw)
In-Reply-To: <mailman.18753.1396458568.10748.help-gnu-emacs@gnu.org>
On Wednesday, April 2, 2014 10:35:12 PM UTC+5:30, Roy Smith wrote:
> Follow-up:
>
>
>
> Not surprisingly, on the "broken" machine, when I do C-h b to look at the keymap, it includes:
>
>
> C-c m Prefix Command
>
> C-c m l pylint
> C-c m n next-error
> C-c m p previous-error
Hi Roy!
Not by way of answer but just reducing the sources of problem:
Have you tried going from global-set-key to define-key on the suitable keymap?
[Sorry I am without emacs ATM so its that vague]
prev parent reply other threads:[~2014-04-05 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 16:53 Custom keybinding getting over-ridden in python mode Roy Smith
2014-04-02 17:05 ` Roy Smith
[not found] ` <mailman.18753.1396458568.10748.help-gnu-emacs@gnu.org>
2014-04-05 16:21 ` Rusi [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=d8ac2507-c9c8-4bf4-bc89-254d7137401a@googlegroups.com \
--to=rustompmody@gmail.com \
--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).