Aaron Gyes
Aaron Gyes
This ought to be installable with `pip`, etc.
I was looking over some issues, and for fun cloned https://gitlab.com/frizlab-demo-projects/swift-argument-parser-example-for-pr-320 which was a test case for a problem that affected bash and not zsh for issue #320. Was just...
I was trying to figure out why some benchmarking of a git.fish completion change I was considering, seemed not to be evidencing the same difference if I used `time`, versus...
So this part, it cannot work with our realpath builtin or with the (FreeBSD?) realpath that macOS comes with: https://github.com/fish-shell/fish-shell/blob/439470b048a628db8fe6dfbf06307e81fdd4e5fa/share/completions/ant.fish#L51-L54 fish realpath: `realpath: These flags are not allowed by fish...
I think the invalid token error rather than the empty expansion error should be shown. Although even the invalid token error could better describe that a value is expected to...
`__fish_complete_proc` prints results like `-fish` for login shells with their `argv[0]` mutated for execve by `login`, or `sh` for e.g. `/bin/bash` executed through a symlink. `killall`, `prep`, etc do not...
I think it would be ideal if e.g. STRING, SEP, and brethren were styled differently than options here: It does happen in the manpages:
The current pager description shown for PATH commands is not super useful. You only are shown these, typically when tab completing a command name, and you are then shown something...
```fish FOO=bar time sleep 1 ``` The parse tree indicates that `time` is expected before the variable assignment list. As in `time FOO=BAR command …` ``` echo time sleep 1...
The should exclude `bar.jpeg` and `bar.c`.