GNU bug report logs - #50459
28.0.50; Python shell completion is incompatible with flex, orderless, etc.

Previous Next

Full log

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

From: João Távora <joaotavora <at> gmail.com>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: 50459 <at> debbugs.gnu.org, Lars Ingebrigtsen <larsi <at> gnus.org>,
 Gregory Heytings <gregory <at> heytings.org>, Augusto Stoffel <arstoffel <at> gmail.com>,
 Michael Albinus <michael.albinus <at> gmx.de>
Subject: Re: bug#50459: 28.0.50; Python shell completion is incompatible with
 flex, orderless, etc.
Date: Fri, 10 Sep 2021 15:06:45 +0100

On Fri, Sep 10, 2021 at 2:28 PM Dmitry Gutov <dgutov <at> yandex.ru> wrote:
>
> On 10.09.2021 16:14, João Távora wrote:
> > - If you're OK with letting the server do the filtering and the
> >    highlighting, you can make a "backend" style like I did for SLY, for
> >    example.  It's going to be faster, but `completion-styles` won't be
> >    honoured.  That's doesn't mean you give up 100% on "flex".  In SLY,
> >    there is flex implemented on the Common Lisp side, and for Eglot, many
> >    LSP server do their own flex matching.
>
> You can't really do that with python-shell completion.

Probably not unless you write some python, no.  I don't see that
as being that dirty.

> Nor do you need
> do: the basic pcmpl mechanism should work just fine with it, and for
> performance the completion table just needs some smarter caching.

Yes, as I said in b), with "sufficiently smart caching" (and infinite
memory space) you can do everything, indeed.  It's one of the
famous "two hard problems" though, so good luck.

João Távora

Previous Next

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