-
Notifications
You must be signed in to change notification settings - Fork 6
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
Can’t get simple zsh completion to work #6
Comments
I'm seeing the same thing with your test case. I will say I am not a completion expert and I've only installed zsh on my system to run the tests which is a barrier to debugging this. I do know the clap completions pass their tests. One thing I noticed that is incorrect that doesn't fix this is that the
Can you reproduce with $ ZDOTDIR=completest-temporary-directory zsh
% foo \t Part of the design for completest is to make it easy for people to drop into the exact shell that is being tested |
BTW, I also accidentally overwrote my
That didn’t work either. What fixed it was the addition of |
Mind creating an issue on how we can clarify this? Since we are writing directly to the directory and there are users today not using a temp directory (clap), we need to make sure this is handled in the right way.
shrug no idea. I guess we could always delete that file when initializing to reduce the chance of bugs I think I had missed that because I copy I do a lot of filesystem shenanigans |
Created #9 :) |
…holder README.md 'Crates Status' icon link
Hi 👋
I’m on macOS, trying to write a simple test case. This just outputs a bunch of files from the current directory, not
bar
, as it should have. When Isource
the completion script from the shell, it works fine.The text was updated successfully, but these errors were encountered: