It seems to have worked so far, yes, though I'm not sure how many people have actually tested it. I will be releasing it as an opt-in, experimental feature in case some issues pop up once people really start using it I did make some modifications to the zsh-capture-completion script to better suit our needs. Instead of running `zsh -f` in the zpty, I just run a function so that the user-defined functions and non-exported variables are still completed. I also modified it not to print completion descriptions and to only return the first generated completion since that's all we need. Some day I would like to look into how difficult it might be to define a new builtin to fetch completion results for a given string. That would be much nicer to work with than this pty trickery. On Sat, Jun 9, 2018 at 9:30 AM Sebastian Gniazdowski wrote: > New autosuggestions is on the way (reddit says), it looks like the > capture-completion zpty-based solution worked? > > On 6 June 2018 at 20:35, Eric Freese wrote: > > Check out https://github.com/Valodim/zsh-capture-completion. > > > > I referenced it recently to implement completion suggestions in > > zsh-autosuggestions: > > https://github.com/zsh-users/zsh-autosuggestions/pull/330 > > > > On Wed, Jun 6, 2018 at 11:43 AM Sebastian Gniazdowski > > wrote: > >> > >> Hello, > >> last commit to the project is from 2013 and I cannot get it up and > >> running. Is anyone familiar with its method of functioning? A friend > >> guesses it pretends key to be pressed after each character, is > >> that true? It would then mean it constantly shows completions under > >> prompt. Is using shell this way actually possible? > >> > >> In general, I'm looking for a method of calling completion functions > >> manually and presenting the results in different form. Does someone > >> know anything about this problem? > >> > >> -- > >> Best regards, > >> Sebastian Gniazdowski > > > > -- > > Sent from my iPhone > -- Sent from my iPhone