You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically, zsh-autosuggestions will continue to offer suggestions of any length, even lengths greater than those specified by ZSH_AUTOSUGGEST_BUFFER_MAX_SIZE. It is set to 20, but it still suggests lines from my history that are longer than 20.
I initially thought ZSH_AUTOSUGGEST_BUFFER_MAX_SIZE was being ignored entirely after trying several numbers and seeing no change, but then I set it as zero and that (correctly) disabled autosuggestions entirely.
Edit: Sorry, forgot to mention. This is zsh 5.5.1 under Cygwin, and I'm using the latest commit of zsh-autosuggestions.
The text was updated successfully, but these errors were encountered:
Set ZSH_AUTOSUGGEST_BUFFER_MAX_SIZE to an integer value to disable autosuggestion for large buffers. The default is unset, which means that autosuggestion will be tried for any buffer size. Recommended value is 20. This can be useful when pasting large amount of text in the terminal, to avoid triggering autosuggestion for too long strings.
The word "buffer" in this case refers to the text you've typed so far into the command line.
So if you've set it to 10, it will stop giving you suggestions after you've typed 11 characters. It has no effect on which suggestions are given.
Basically, zsh-autosuggestions will continue to offer suggestions of any length, even lengths greater than those specified by ZSH_AUTOSUGGEST_BUFFER_MAX_SIZE. It is set to 20, but it still suggests lines from my history that are longer than 20.
I initially thought ZSH_AUTOSUGGEST_BUFFER_MAX_SIZE was being ignored entirely after trying several numbers and seeing no change, but then I set it as zero and that (correctly) disabled autosuggestions entirely.
Edit: Sorry, forgot to mention. This is zsh 5.5.1 under Cygwin, and I'm using the latest commit of zsh-autosuggestions.
The text was updated successfully, but these errors were encountered: