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

Previous Next

Full log

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

From: João Távora <joaotavora <at> gmail.com>
To: Pankaj Jangid <pankaj <at> codeisgreat.org>
Cc: 48609 <at> debbugs.gnu.org, Doug Davis <ddavis <at> ddavis.io>,
 Andrii Kolomoiets <andreyk.mad <at> gmail.com>
Subject: Re: bug#48609: Eglot and tab-always-indent conflict in python-mode
Date: Tue, 25 May 2021 10:32:52 +0100

Pankaj Jangid <pankaj <at> codeisgreat.org> writes:

> Andrii Kolomoiets <andreyk.mad <at> gmail.com> writes:
>
>> 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.
>
> Thanks for sharing this. I think I should have been more specific. The
> bug is more related to python-mode then to ‘tab-always-indent’.
>
> In ‘python’ buffers, TABs cycle position of point. But as described in
> my original report and reproduced by João, bringing Eglot, inhibits this
> behavior.

Yes, but what actually happened is that the one of those tabs was
waiting for completions to come in, so the system was indeed behaving as
intended.  It's just that when you don't have Eglot, you also don't have
completions.

João

Previous Next

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