|
From: | Dmitry Gutov |
Subject: | bug#50459: 28.0.50; Python shell completion is incompatible with flex, orderless, etc. |
Date: | Fri, 10 Sep 2021 16:32:52 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 |
On 09.09.2021 19:46, Augusto Stoffel wrote:
To alleviate this, the completion-at-point function could implement some sort of caching. The difficult question is when to invalidate the cache. I've attached one possiblility as a draft patch. If the approach seems reasonable, then I'll format it properly.
It's much simpler than what we talked about, but given that python-shell-completion-at-point doesn't really look past the current line, your approach should work fine.
I'm not very familiar with the code, so I cannot approve the exact patch, though, sorry.
As a bonus, though, maybe add the position of prompt on the shell-buffer to the invalidation key? Like, if a user imports some new lib in there, that can bring in new completions.
[Prev in Thread] | Current Thread | [Next in Thread] |