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

#RUN: %fish -C 'set -l fish %fish' %s | %filter-ctrlseqs

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: alpha
# CHECK: bravo
# CHECK: india
# CHECK: foxtrot
# CHECK: hotel
# CHECK: golf
# CHECK: charlie
# CHECK: delta
# CHECK: echo
# CHECK: juliett
# CHECK: kilo
# CHECK: lima
Extended & human-friendly keys See the changelog additions for user-visible changes. Since we enable/disable terminal protocols whenever we pass terminal ownership, tests can no longer run in parallel on the same terminal. For the same reason, readline shortcuts in the gdb REPL will not work anymore. As a remedy, use gdbserver, or lobby for CSI u support in libreadline. Add sleep to some tests, otherwise they fall (both in CI and locally). There are two weird failures on FreeBSD remaining, disable them for now https://github.com/fish-shell/fish-shell/pull/10359/checks?check_run_id=23330096362 Design and implementation borrows heavily from Kakoune. In future, we should try to implement more of the kitty progressive enhancements. Closes #10359 2024-03-30 23:10:12 +08:00			`#RUN: %fish -C 'set -l fish %fish' %s \| %filter-ctrlseqs`
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: alpha`
			`# CHECK: bravo`
			`# CHECK: india`
			`# CHECK: foxtrot`
			`# CHECK: hotel`
			`# CHECK: golf`
			`# CHECK: charlie`
			`# CHECK: delta`
			`# CHECK: echo`
			`# CHECK: juliett`
			`# CHECK: kilo`
			`# CHECK: lima`