pylint #3855 emacs keybindings in pylint.el [resolved]
pylint.el binds [f1], [f2] and [f3] in the python mode map, without asking. It should not. I personally feel that pylint.el should not bind any keys at all. If you feel pylint.el really must bind keys, I would draw your attention to the recommendations of the Emacs Lisp manual, such as The key sequences bound in a minor mode should consist of C-c' followed by one of `.,/?'"[]|~!#$%^&*()-_+='. (The other punctuation characters are reserved for major modes.) Also note that next-error is (apparently) already bound to C-x ` in all buffers. I strongly feel that mode-local bindings for next-error and/or previous-error are also quite silly. Finally, I advise you to use EVAL-AFTER-LOAD (and DEFINE-KEY) instead of a hook, since the forms in python.el really only need to be evaluated once per emacs process, not every time the user opens a Python file. | |
| priority | normal |
|---|---|
| type | bug |
| done in | 0.21.4 |
| load | 0.200 |
| load left | 0.000 |
| closed by | <not specified> |
Comments
-
2009/09/02 06:24, written by anon
add commentI've recently committed a patch to give pylint a more sensible set of key-bindings and it's been merged into trunk as r480 by Adrien.
In the patch I chose to bind pylint, next-error and previous-error to a C-c m prefix to mimic ropemacs. The bindings are local to the python-mode-map. I chose to still supply default bindings because the C-x ` and M-g p make are on 2 different end of the keyboards with no relation to each other whatsoever. Supplying a local binding makes sense for people who don't use other modes as often as python-mode and so are not used to the default key-bindings for next and previous error. Since this is bound locally to the mode key-map, the global key-bindings are not disturbed and you can still use them if you want.