|April 28th, 2017|
|code, python, tech [amp]|
class Foo(): def a(): return 'foo' class Bar(): def a(): return 'bar' def baz(b: Foo) -> str: return b.a
What I don't like about jedi-mode is that it also turns on other distracting things that get in the way of trying to write. If you hold the cursor still it pops up "quick help" that obscures the code below:
If you start to type something it recognizes it offers a completion, and if you press the wrong key you'll accidentally accept the completion:
And if you type something ambigous it can do both frustrating things at once:
I put up with this for a surprisingly long time before looking into fixing it, but these can be disabled. The key thing is that jedi-mode turns on auto-complete-mode, and it's auto-complete that's responsible for most of the behavior I don't like. So: here's how to turn on jedi in a non-instrusive way:
; move quick-help tooltips to the minibuffer (setq jedi:tooltip-method nil) ; don't auto-complete unless requested (setq ac-auto-start nil) (setq ac-auto-show-menu nil) (define-key ac-mode-map (kbd "M-TAB") 'auto-complete) (add-hook 'python-mode-hook 'jedi:setup)
I'm pretty happy, but there are still two things I'd like:
- C-c , on an empty stack should bring up a list of places a thing is used. That is, places where C-c . would bring you here.
- Automated refactoring: rope has fallen way behind and can't handle python 3 codebases well. I'd love to be able to write "turn all calls to package.foo(...) into package._foo(...)" rules and have jedi automatically apply them.