Breakage after typing a [

[ivan]

This happens with 0.4.0, but not 0.3.3:

at@ra:/home/at# while [       
at@ra:/home/at# cd bin                    
at@ra:/home/at/bin:master# while [       
_zsh_autosuggest_strategy_match_prev_cmd:17: bad math expression: operator expected at `bin'
at@ra:/home/at/bin:master# while [
at@ra:/home/at/bin:master# while [       
_zsh_autosuggest_strategy_match_prev_cmd:17: bad math expression: operator expected at `bin'
at@ra:/home/at/bin:master# while [
at@ra:/home/at/bin:master# [
_zsh_autosuggest_strategy_match_prev_cmd:17: bad math expression: operator expected at `bin'
at@ra:/home/at/bin:master# [
at@ra:/home/at/bin:master# [
_zsh_autosuggest_strategy_match_prev_cmd:17: bad math expression: operator expected at `bin'
at@ra:/home/at/bin:master# [
at@ra:/home/at/bin:master# [
_zsh_autosuggest_strategy_match_prev_cmd:17: bad math expression: operator expected at `bin'
at@ra:/home/at/bin:master# [
at@ra:/home/at/bin:master# ]]]][
_zsh_autosuggest_strategy_match_prev_cmd:17: bad math expression: operator expected at `bin'

The _zsh_autosuggest_strategy_match_prev_cmd error pops up immediately after pressing the [ key.

# zsh --version                                               
zsh 5.1.1 (x86_64-ubuntu-linux-gnu)

.zshrc settings: https://gist.github.com/ivan/79de5e87210e8cf21e305bb4c30c4360#file-zshrc-L200-L206 possibly-relevant bit being

ZSH_AUTOSUGGEST_STRATEGY=match_prev_cmd

[ericfreese]

Looks like this is specific to match_prev_cmd strategy.

[Birne94]

I am receiving a similar error with the latest release (master @ 2cb6eb6 - (tag: v0.4.0)) when pressing the number sign (#):

daniel@Daniels-MBP ~/Workspace/dotfiles % #
_zsh_autosuggest_strategy_match_prev_cmd:17: bad math expression: operator expected at `ZSH_AUTOSU...'
daniel@Daniels-MBP ~/Workspace/dotfiles % #

[paulbdavis]

I am having the same thing happen as @Birne94 except only on my remote machine. I have the same config in my local setup (both have the plugin up to date with master) and it can type # just fine

It does not have a problem typing a [ character

[arizonahanson]

I "fixed" this by changing the _zsh_autosuggest_strategy_match_prev_cmd() to escape the match key (and then rebuilding the main file with make).

--- a/src/strategies/match_prev_cmd.zsh
+++ b/src/strategies/match_prev_cmd.zsh
@@ -26,7 +26,7 @@ _zsh_autosuggest_strategy_match_prev_cmd() {
        # Get all history event numbers that correspond to history
        # entries that match pattern $prefix*
        local history_match_keys
-   history_match_keys=(${(k)history[(R)$prefix*]})
+  history_match_keys=(${(k)history[(R)${(b)prefix}*]})
 
        # By default we use the first history number (most recent history entry)
        local histkey="${history_match_keys[1]}"

not entirely sure if this is the best solution

[arizonahanson]

made a pull request: #267

[ericfreese]

Should be fixed now on develop.