Get flymake-cursor.el and save it as ~/.emacs.d/vendor/flymake-cursor.el.
PYMACS ROPE AQUAMACS INSTALL
Note: pip install does not work with v0.25.
PYMACS ROPE AQUAMACS CODE
rope-code-assist, M-/ Code completion rope-rename, C-c r r Rename a variable, function, etc. For more information, look in the Rope menu. It supports code completion, renaming, and other refactoring. Ropemacs is an Emacs plugin to use Rope, a powerful Python refactoring library. For a complete list, open a Python file and run M-x apropos RET python RET python-shift-left, C-c C-< Decrease indentation of the region python-shift-right, C-c C-< Increase indentation of the region python-switch-to-python, C-c C-z Start (or switch) to a Python shell python-send-buffer, C-c C-c Run the current buffer in the Python interpreter python-send-region, C-c C-r Run the selected code in the Python interpreter python-describe-symbol, C-c C-f Get help on a Python symbol (Better than visiting the slow Python website, right?) Configuration ( ~/.emacs changes) (setq-default indent-tabs-mode nil) use only spaces and no tabs
I am currently using the default python.el included with Emacs 23. The first version of python.el was included in Emacs 22 and an improved version was included in Emacs 23. There are two Python modes: python-mode.el created by the Python community and python.el created by the Emacs community (David Love). I highly recommend you give Jedi and Jedi.Date: | Modified: | Tags: emacs, notestoself, python | 15 Comments Python mode ¶ I haven’t used Jedi and Jedi.el long enough to really get to know it, but I’m probably going to extend Jedi.el so it uses eldoc-mode for displaying the function parameters it’s also a bit rough around the edges, and I may want to tweak certain things to my liking, but overall: huge success! And finally, it can show the documentation for the identifier at point (be it a class or function) with C-c d. It also has a “related names” functionality, tracking down same-named identifiers in other modules it uses Anything (now Helm) to display the results, and it is bound to C-c r. The Jedi.el module also Just Works with the excellent auto-complete library, as you can see in the picture above.Īside from completion, it also offers “find symbol definition at point” (a la TAGS, but not crap) and Jedi.el sensibly binds it to C. It seems to resolve, simplistically (which is good), as many assignments and method calls as one can reasonably expect from a non-evaluating, statically analyzing Python completion library. Imagine my surprise, after fidgeting with the dependencies for both Jedi and Jedi.el, the Emacs library for Jedi, that it… works! And it’s good! It’s up-and-coming, I should say, but perfectly usable it doesn’t get in my way, it’s got some crazy deferreds library it depends on for asynchronous, non-blocking querying of Jedi, but that bit works great – no input lag at all. The other alternative is the 600 lbs gorilla, CEDET, and its incomplete Python support, but that’s no good either. So I never really used them, and lived without completion or, well, much of anything beyond the REPL and my own handcrafted modifications. Slow, crash-prone, obtuse and impossible to extend. I’ve experimented with Pymacs – an interesting science project that adds “Python-like” support Emacs, so you can avoid interacting with Elisp, except not really – rope, and ropemacs and they were… disappointing. Yes, Jedi, an editor-agnostic library that publishes auto completion, docstring support, and more. If you’re using Python with Emacs (using one of several competing, incompatible, and slightly different modes) you are used to a pretty… bare-bones experience: no completion semi-functional dynamic docstring support and little in the way of two-way communication between Python and Emacs.Įnter Jedi, a completion library.