Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

menu-complete gets stuck when new match dir is same length as previous match dir #48

Closed
chrisant996 opened this issue Jan 2, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@chrisant996
Copy link
Owner

chrisant996 commented Jan 2, 2021

menu-complete gets stuck when a previous match dir and new match dir are the same length.

REPRO:

  • For example, in the clink repo, where clink\lib\ and clink\lua\ both exist.
  • Type dir cli,menu-complete,l,menu-complete,menu-complete,s,menu-complete.

EXPECTED: completion is clink\lua\scripts\.
ACTUAL: nothing happens, because clink\lib\s* doesn't exist ("lib\s*" is used by mistake instead of "lua\s*").

This regression was introduced in the v1.0.0 rewrite, as part of the match_pipeline stuff.

@chrisant996 chrisant996 added the bug Something isn't working label Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant