fish-shell/share/completions/pipenv.fish

if command -sq pipenv
    # pipenv determines which completions to print via some automagic that might not be perfect.
    # Force it to be correct.
    _PIPENV_COMPLETE=source-fish pipenv --completion 2>/dev/null | source
end

complete -c pipenv -n "__fish_seen_subcommand_from run" -a "(__fish_complete_subcommand --fcs-skip=2)" -x
Python's pip and pipenv completions (#4448) * Add pip completion * We call native pip completion for fish if pip is installed * Add pipenv completion * We call pipenv native completion if pipenv is installed * Applied changes as requested by @floam * Changed usage of `test (command -v)` for just `command -sq` * Add completions for pip2/3 * In some systems pip is not aliased and we have pip2 and pip3 * In those cases, we just load the completions for those commands * Separate pip2/3 completions in their own file as requested by @floam 2017-10-05 15:15:41 +11:00			`if command -sq pipenv`
completions/pipenv: Really force it to print fish completions "To assume" and such. It doesn't check $SHELL, so it might have some other automagic that can fail (probably still because of the login shell, but I have no idea). Override the special variable that click-completion (https://github.com/click-contrib/click-completion) uses to force it instead. Really fixes #6454. [ci skip] 2019-12-25 16:29:10 +01:00			`# pipenv determines which completions to print via some automagic that might not be perfect.`
			`# Force it to be correct.`
Run fish_indent on all our fish scripts It's now good enough to do so. We don't allow grid-alignment: ```fish complete -c foo -s b -l barnanana -a '(something)' complete -c foo -s z -a '(something)' ``` becomes ```fish complete -c foo -s b -l barnanana -a '(something)' complete -c foo -s z -a '(something)' ``` It's just more trouble than it is worth. The one part I'd change: We align and/or'd parts of an if-condition with the in-block code: ```fish if true and false dosomething end ``` becomes ```fish if true and false dosomething end ``` but it's not used terribly much and if we ever fix it we can just reindent. 2020-01-13 20:34:22 +01:00			`_PIPENV_COMPLETE=source-fish pipenv --completion 2>/dev/null \| source`
Python's pip and pipenv completions (#4448) * Add pip completion * We call native pip completion for fish if pip is installed * Add pipenv completion * We call pipenv native completion if pipenv is installed * Applied changes as requested by @floam * Changed usage of `test (command -v)` for just `command -sq` * Add completions for pip2/3 * In some systems pip is not aliased and we have pip2 and pip3 * In those cases, we just load the completions for those commands * Separate pip2/3 completions in their own file as requested by @floam 2017-10-05 15:15:41 +11:00			`end`
Complete `pipenv run` 2020-10-25 19:00:58 +01:00
			`complete -c pipenv -n "__fish_seen_subcommand_from run" -a "(__fish_complete_subcommand --fcs-skip=2)" -x`