Emacs python code#

Emacs python code#

Reading that code shows me how it interacts with the inferior buffer, etc. For instance, to integrate with eldoc-mode, it defines a function called python-eldoc-function and gives that to the eldoc module for use in python buffers. From there I started looking at the source code.

It's author has kindly put a brief summary of what the mode can do which mentions eldoc-mode, Imenu, outline-mode, hippie-expand, rlcompleter, abbrev tables, and a bunch of other things. Then I asked for help about this strange new mode ( C-h m) to see what it could do. I didn't actually have any python code available, so I just went to my scratch buffer and made it a python buffer ( M-x python-mode). This allows rapid switching between projects, starting anywhere, whether already in a project or not. consult-jump-project features the 'project' file and buffer categories from consult-buffer, and adds an always-present '(Other) Projects' category (courtesy project.el). My first step was to open a file in python-mode. I tend to work with lots of projects at the same time and wanted a quick way to switch between them. In the spirit of helping others to help themselves, I'd like to point out how I came upon all of this information. It looks to be a pretty complete setup, and even claims to have live warning/error detection. If I were going to do a lot of python programming and didn't already have a fairly complicated emacs set up, I'd probably start by installing emacs-for-python. A little poking around shows several related solutions for this, all of which seem to rely on pymacs. The documentation says that it can integrate with hippie-expand for exact completions, but this might be a lie I couldn't figure out how it works. More sophisticated is hippie-expand, but even that doesn't do anything python-specific. This is a fairly simple form of completion it's just meant to work on any old file you happen to edit. By default you have access to dabbrev-expand by hitting M-/.

Perhaps it's just my setup, or perhaps I'm reading the wrong source files it's hard to say.Įmacs provides several different types of expansion/autocompletion. I spent a few minutes poking around in the source code and everything seems to be in place, but the code that it runs in the inferior process is just returning an empty string. Now, at this point I have to say that I don't do any regular python programming, and that when I tried it just now it didn't work. You can turn it on automatically for all new python-mode buffers with (add-hook 'python-mode-hook '(lambda () (eldoc-mode 1)) t) in your emacs startup file.

It talks to an inferior python buffer to inspect the functions directly, so it should always be decently accurate. Just do M-x eldoc-mode while you're in a python file to turn it on and it should start working. Python-mode can integrate with eldoc-mode to display the arg spec of the function you're calling at point.