Marlon Richert

It’s expected behavior, as documented in the part of the Readme that you linked to.

How do you expect to find commands from history that start with `git `, if you don't have any of those in your history? But I could add a message...

> ``` > % git > external command > git-receive-pack git-shell git-upload-archive git-upload-pack > common substring: git- > ``` Did you type a space after typing `git`? It looks like...

> Yes, I dit type space, you can see it here Your earlier example showed that completion strangely enough didn’t yet notice that you had typed a space: > %...

Can you run the test session again, try reproducing the bug until it occurs, and then share the contents of the files `$_autocomplete__log`, `$_autocomplete__log_async` and `$_autocomplete__log_pty` here?

Yes, please share the part of the logs corresponding to the moment the bug occurred.

@underlow Can you try to find out what in your normal config causes the bug to occur?

Well, check what is the difference between your normal environment and the test environment. For example, check the output of `env`.

I read your comments again and it looks like autocompletion is started correctly, but it never finishes. When the bug occurs, do you find that there are zombie `zsh` processes...

How is it possible that `ZSH=/Users/user/.oh-my-zsh` gets set in your test environment? The shell session you pasted above did not include Oh-My-Zsh in the `.zshrc` file.