Document caveats of match_prev_cmd strategy #161

Closed
wants to merge 1 commit into
from

2 participants

@tsdh

This strategy relies on the history being exactly in the order in which
commands have been entered. Therefore, options like suppressing
duplicates or expiring duplicates first will lead to unexpected
suggestions.

@tsdh tsdh Document caveats of match_prev_cmd strategy
This strategy relies on the history being exactly in the order in which
commands have been entered.  Therefore, options like suppressing
duplicates or expiring duplicates first will lead to unexpected
suggestions.
a159981
@ericfreese
zsh-users member

Thanks for the PR! I've just changed the branching scheme so all PRs should come in to the develop branch instead of master. Can you please re-submit your PR to the develop branch?

@ericfreese ericfreese closed this May 28, 2016
@tsdh

Done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment