You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was including /home/linuxbrew/.linuxbrew/share/fish/vendor_completions.d/urm.fish in my fish shell, and found this error;
> source /home/linuxbrew/.linuxbrew/share/fish/vendor_completions.d/urm.fish
complete: Too many arguments
/home/linuxbrew/.linuxbrew/share/fish/vendor_completions.d/urm.fish (line 5):
complete -c urm -s i -l prompt before every removal
^
from sourcing file /home/linuxbrew/.linuxbrew/share/fish/vendor_completions.d/urm.fish
5: complete -c urm -s i -l -d 'prompt before every removal'
The -l requires an option here's my fix.
complete -c urm -s i -l prompt -d 'prompt before every removal'
However I'm assuming the completions are auto-generated
It seems something in the urm code has before every removal in the incorrect place, it should be aligned with the column on the right.
I tried to find it in the code, but I'm no rust developer yet.
> brew info uutils-coreutils
uutils-coreutils: stable 0.0.14 (bottled), HEAD
> urm --version
urm 0.0.14
Thanks!
The text was updated successfully, but these errors were encountered:
The completions are indeed autogenerated by clap-complete. If you can find a minimal, easy to reproduce example of this problem, we could open an issue there.
Edit: Actually the --prompt before every removal line indeed doesn't look right, arguments are not supposed to have spaces😄 This might be a mistake on our part, I'll look into it.
I was including /home/linuxbrew/.linuxbrew/share/fish/vendor_completions.d/urm.fish in my fish shell, and found this error;
The -l requires an option here's my fix.
However I'm assuming the completions are auto-generated

It seems something in the urm code has
before every removal
in the incorrect place, it should be aligned with the column on the right.I tried to find it in the code, but I'm no rust developer yet.
Thanks!
The text was updated successfully, but these errors were encountered: