fish-shell/tests/checks/complete-group-order.fish

#RUN: %fish -C 'set -l fish %fish' %s

function fooc; true; end;

# A non-`complete -k` completion
complete -c fooc -fa "alpha delta bravo"

# A `complete -k` completion chronologically and alphabetically before the next completion. You'd
# expect it to come first, but we documented that it will come second.
complete -c fooc -fka "golf charlie echo"

# A `complete -k` completion that is chronologically after and alphabetically after the previous
# one, so a naive sort would place it after but we want to make sure it comes before.
complete -c fooc -fka "india foxtrot hotel"

# Another non-`complete -k` completion
complete -c fooc -fa "kilo juliett lima"

# Generate completions
complete -C"fooc "
# CHECK: india
# CHECK: foxtrot
# CHECK: hotel
# CHECK: golf
# CHECK: charlie
# CHECK: echo
# CHECK: alpha
# CHECK: bravo
# CHECK: delta
# CHECK: juliett
# CHECK: kilo
# CHECK: lima
tests: filter control sequences only when interactive This demonstrates that we only write control sequences when interactive. 2024-04-12 18:19:32 +08:00			`#RUN: %fish -C 'set -l fish %fish' %s`
Test `complete` builtin sort of (sorted + unsorted) completions Like the pexpect-based pager compeltions test `complete-group-order.py`, but for the `complete` builtin. Verifies the same sort/dedup rules that apply to the pager are also applied to the output of `complete` and asserts the sort behavior for multiple `complete -k` calls for the same command and with the same (or with both passing) preconditions. 2022-11-01 05:52:44 +08:00
			`function fooc; true; end;`

			# A non-`complete -k` completion
			`complete -c fooc -fa "alpha delta bravo"`

			# A `complete -k` completion chronologically and alphabetically before the next completion. You'd
			`# expect it to come first, but we documented that it will come second.`
			`complete -c fooc -fka "golf charlie echo"`

			# A `complete -k` completion that is chronologically after and alphabetically after the previous
			`# one, so a naive sort would place it after but we want to make sure it comes before.`
			`complete -c fooc -fka "india foxtrot hotel"`

			# Another non-`complete -k` completion
			`complete -c fooc -fa "kilo juliett lima"`

			`# Generate completions`
			`complete -C"fooc "`
			`# CHECK: india`
			`# CHECK: foxtrot`
			`# CHECK: hotel`
			`# CHECK: golf`
			`# CHECK: charlie`
			`# CHECK: echo`
complete: Sort --keep-order completions smaller This should make the sort have a strict weak ordering, which rust requires since 1.81 (or it will panic). Note: This changes the order, but that's fine since the current order is random weirdness anyway. Fixes #10763 2024-10-04 22:50:40 +08:00			`# CHECK: alpha`
			`# CHECK: bravo`
			`# CHECK: delta`
Test `complete` builtin sort of (sorted + unsorted) completions Like the pexpect-based pager compeltions test `complete-group-order.py`, but for the `complete` builtin. Verifies the same sort/dedup rules that apply to the pager are also applied to the output of `complete` and asserts the sort behavior for multiple `complete -k` calls for the same command and with the same (or with both passing) preconditions. 2022-11-01 05:52:44 +08:00			`# CHECK: juliett`
			`# CHECK: kilo`
			`# CHECK: lima`