6 commits

Author	SHA1	Message	Date
Eric Freese	c04e015d13	Add to explanation of extra stuff after zpty -r	2019-06-15 21:17:58 -06:00
Eric Freese	e9ce05c4c1	Ensure that kill succeeds even in older buggy versions of zsh ... See https://unix.stackexchange.com/a/477647/156673	2019-06-15 21:17:58 -06:00
Eric Freese	fdf4502c5c	We need to autoload is-at-least for it to be available ... This error was hidden inside the zpty	2019-06-15 21:17:58 -06:00
Eric Freese	7e048c3f53	Fix error that was hidden in zpty ... Without the quotes, this was blowing up with: _zsh_autosuggest_capture_postcompletion:unset:5: not enough arguments	2019-06-15 21:17:58 -06:00
Eric Freese	2b05f5ed2d	Add a comment explaining post-completion hook	2019-06-15 21:17:58 -06:00
Eric Freese	c1910348c7	Implement completion suggestion strategy (#111) ... Based on https://github.com/Valodim/zsh-capture-completion `zpty -r` with a pattern seems to have some funky behavior on older versions, giving unpredictable results Don't use `-s` option to `zmodload`. It is not available in zsh versions older than 5.3 If running in sync mode and a completion takes a long time, the user can ^C out of it. We need to use `always` in the strategy function or the pty will not be destroyed in this case and the next time we go to create it, it will fail, making the shell unusable. User can have many different completion styles set that will modify what they've already typed. These styles will result in suggestions that don't match what the user has already typed. We try our best to unset some of the more problematic ones, but add some code to fetch to invalidate suggestions that don't match what the user's already typed.	2019-04-11 09:53:55 -06:00