|Subject:||Recommendation for CAPF setup when you don't know completion string in advance|
|Date:||Sat, 3 Apr 2021 18:23:28 -0400|
I’m endeavoring to more fully link completion in python-shell-mode directly to those provided by iPython, when it is running as the inferior shell. Modern versions of iPython have fantastic built-in completion capabilities when run in a terminal, but they are not well exploited by python.el.
Here’s the logical flow I’m trying to achieve:
In principle I could just do this directly in the CAPF, i.e. interact with the iPython process, compute `beg’ and `end’, return them with the completion list as the collection. But as Programmed Completions node says:
So it’s a quandary: I won’t yet know `beg’ and `end’ until _after_ interacting with iPython. Is there any way to “revise” ‘beg’ and ‘end’ in a collection function returned from a CAPF? If not, other ideas I could try?
|[Prev in Thread]||Current Thread||[Next in Thread]|