fish-shell/share/completions/clang.fish

# Multiple versions are often installed as clang, clang-7, clang-8, etc.
# They won't be autoloaded, but once clang++ is used once, they'll gain completions too.
# This could potentially be moved to __fish_config_interactive.fish in the future.

# This pattern unfortunately matches clang-format, etc. as well.
complete -p '*clang*' -n __fish_should_complete_switches -xa '(__fish_complete_clang)'
complete -c clang -n 'not __fish_should_complete_switches' \
    -k -xa "(__fish_complete_suffix .o .out .c .cpp .so .dylib)"

# again but without the -x this time for the pattern-matched completion
complete -p '*clang*' -n 'not __fish_should_complete_switches' \
    -k -a "(__fish_complete_suffix .o .out .c .cpp .so .dylib)"
Add dynamic clang completions via clang --autocomplete Use clang/clang++'s own autocompletion support to complete arguments. It is rather convoluted as clang generates autocompletions for a portion of the current token rather than the entire token, e.g. while `--st` will autocomplete to `--std=` (which is fine by fish), `--std=g` will autocomplete to `gnu...` without the leading `--std=` which breaks fish' support for the completion. Additionally, on systems where clang/clang++ is the system compiler (such as FreeBSD), it is very often for users to invoke a newer version of clang/clang++ installed as clang[++]-NN instead of clang. Using a monkey-patched version of `complete -p` to support that without breaking (future) completions for commands like `clang-format`. Closes #4174. 2018-10-23 12:53:20 +08:00			`# Multiple versions are often installed as clang, clang-7, clang-8, etc.`
			`# They won't be autoloaded, but once clang++ is used once, they'll gain completions too.`
			`# This could potentially be moved to __fish_config_interactive.fish in the future.`

			`# This pattern unfortunately matches clang-format, etc. as well.`
Reindent functions to remove useless quotes This does not include checks/function.fish because that currently includes a "; end" in a message that indent would remove, breaking the test. 2020-03-10 02:36:12 +08:00			`complete -p 'clang' -n __fish_should_complete_switches -xa '(__fish_complete_clang)'`
			`complete -c clang -n 'not __fish_should_complete_switches' \`
Fixes #8924 via `__fish_complete_suffix` overhaul Before: * hand write arg parse * only accepts one suffix After: * use `arg_parse` to parse args * accepts multi suffixes Closes #9611. 2023-02-24 10:18:08 +08:00			`-k -xa "(__fish_complete_suffix .o .out .c .cpp .so .dylib)"`
Stop using __fish_complete_suffix with a braced argument __fish_complete_suffix accepts a first argument containing a brace-expansion, like __fish_complete_suffix '.{c,cpp,py}' We're gonna be removing the `eval` that does that shortly, so let's remove all uses in our code. 2019-12-29 00:00:48 +08:00
Add dynamic clang completions via clang --autocomplete Use clang/clang++'s own autocompletion support to complete arguments. It is rather convoluted as clang generates autocompletions for a portion of the current token rather than the entire token, e.g. while `--st` will autocomplete to `--std=` (which is fine by fish), `--std=g` will autocomplete to `gnu...` without the leading `--std=` which breaks fish' support for the completion. Additionally, on systems where clang/clang++ is the system compiler (such as FreeBSD), it is very often for users to invoke a newer version of clang/clang++ installed as clang[++]-NN instead of clang. Using a monkey-patched version of `complete -p` to support that without breaking (future) completions for commands like `clang-format`. Closes #4174. 2018-10-23 12:53:20 +08:00			`# again but without the -x this time for the pattern-matched completion`
			`complete -p 'clang' -n 'not __fish_should_complete_switches' \`
Fixes #8924 via `__fish_complete_suffix` overhaul Before: * hand write arg parse * only accepts one suffix After: * use `arg_parse` to parse args * accepts multi suffixes Closes #9611. 2023-02-24 10:18:08 +08:00			`-k -a "(__fish_complete_suffix .o .out .c .cpp .so .dylib)"`