[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Python completion when using pdb (M-x pdb)

From: Maxim Cournoyer
Subject: Python completion when using pdb (M-x pdb)
Date: Tue, 23 May 2017 09:06:04 -0700
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)

Hello Emacs!

I've recently discovered that Emacs provides it's own completion
mechanism, for example when running M-x run-python. This works even with
the vanilla Python interpreter, which doesn't provide such completion
out-of-the-box itself, which is nice!

However, I couldn't make completion work in pdb. My understanding, when
searching on the web, is that it *should* work in pdb too. For example,
the commit a92066b (python.el: Fix completion for pdb interactions) made
two years ago would suggest that it should work.

Things I've tried:

1. Using M-x pdb: The buffer is not even set up for completion with
python.el. C-h k <TAB> reveals that it simply calls

2. Once debugging, I used 'M-x run-python'. The Python process "inherited"
the already running pdb process and I could see the (Pdb) prompt from
there. (The same could have been attained by M-x run-python at first,
then execfile some/file (python 2) in wich "import pdb; pdb.set_trace()"
is used.

This time, C-h k <TAB> revealed it was bound to
`python-shell-completion-complete-or-indent', which is better. However,
attempting to tab-complete any symbol at the pdb prompt returned 'No
match' at the minibuffer.

I also tested with realgud instead of gud, with the same result.

Any pointers would be very appreciated :)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]