GNU bug report logs - #48609
Eglot and tab-always-indent conflict in python-mode

Previous Next

Full log

Message #20 received at 48609 <at> debbugs.gnu.org (full text, mbox):

From: Andrii Kolomoiets <andreyk.mad <at> gmail.com>
To: João Távora <joaotavora <at> gmail.com>
Cc: 48609 <at> debbugs.gnu.org, Doug Davis <ddavis <at> ddavis.io>,
 pankaj <at> codeisgreat.org
Subject: Re: bug#48609: Eglot and tab-always-indent conflict in python-mode
Date: Mon, 24 May 2021 11:17:54 +0300

João Távora <joaotavora <at> gmail.com> writes:

> So I'm not sure what needs to be fixed here, if anything, or how you
> would like this to behave.

IMO works as described in the `tab-always-indent` docstring:

If ‘complete’, TAB first tries to indent the current line, and if the line
was already indented, then try to complete the thing at point.

One can reproduce this without Eglot:

1. emacs -Q
2. C-x C-f test.py
3. M-: (setq tab-always-indent 'complete)
4. C-c C-p

After step 4 the `python-completion-at-point` function starts producing
completions and each TAB key will lead to "No match" message.

Pankaj, take a look at the `tab-first-completion` variable.


--
Andrii

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.