Eric Freese

You should be able to hook this in pretty easily by implementing a new suggestion strategy and specifying it in your configuration. See e.g. https://github.com/zsh-users/zsh-autosuggestions/blob/a411ef3e0992d4839f0732ebeb9823024afaaaa8/src/strategies/completion.zsh

I have been trying to wrap my head around this today. I'm having trouble with the specifics of the situation you've outlined, but I do think I've found a (different?)...

I've broken out some of your changes into a separate branch here: https://github.com/zsh-users/zsh-autosuggestions/compare/develop...fixes/romkatv-async-fixes I tacked the `_ZSH_AUTOSUGGEST_ASYNC_FD` fix mentioned above on the end. I'm curious if that fixes the issues...

I just realized that #630 contained this `_ZSH_AUTOSUGGEST_ASYNC_FD` fix and I've merged that to `develop`. I'm fairly sure that this will fix the issues you're seeing, and is a less...

Ok, thanks. I'm still trying to get my head around this. Is this an example of what you're thinking? Please correct/extend this example to illustrate the scenario you're thinking of...

- Writing custom suggestion strategies

- Smarter context sensitive suggestions like fish has

I pushed a failing spec to `fixes/kill-multiple-words` ``` multiple words killed with `backward-kill-word` can be yanked back with `yank` (FAILED - 1) Failures: 1) multiple words killed with `backward-kill-word` can...

Looks like this behavior can be reproduced by simply wrapping `backward-kill-word` in a user-defined widget. ```shell % my-backward-kill-word() { zle backward-kill-word } % zle -N my-backward-kill-word % bindkey ^W my-backward-kill-word...

The functionality where cut text is concatenated to be yanked in combined form later seems to be dependent on the two built-in cutting widgets running one directly after the other....