-
Notifications
You must be signed in to change notification settings - Fork 3
Inconsistent with default completion behavior in simpler cases #10
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
Comments
@geekscrapy, now completion should work as you described |
Thanks, I just tested and I get odd behavior - using commit 7885c8e. The following gets printed to the terminal as part of the auto-complete:
^ The last line is what I would expect (as the second option to complete), and the unexpected behavior being the printout of the following path one the first time is pressed. As you can see, "umes/" is the correct first auto suggestion, which is printed after the random path.
|
I understand what that garbage output means, but there are multiple places where it could've come from. Since this does not happen on my machines (Linux, Windows), it may be related to some little differences in GNU and BSD tooling. Can you help me with debugging?
|
|
Aha, I see. Looks like you've set up a handy alias for rm :) I'll add a workaround for such cases, you don't need to change your configuration. |
I fixed this in |
Looks to have fixed it! |
Ok, I've merged the changes into |
Reported by @geekscrapy in comments:
I confirm the reported behavior. Issue affects only directory completion.
File completion (try
ls
) works almost as expected, but double slashes should be dropped.The text was updated successfully, but these errors were encountered: