From 34c2bf0f55673d6a89d24705a9aa68afeaa9944e Mon Sep 17 00:00:00 2001 From: Mahmoud Al-Qudsi Date: Mon, 24 Jul 2017 17:55:49 -0500 Subject: [PATCH] Using new complete --keep-order option for __fish_git_recent_commits The primary motivation for --keep-order for `complete` was to support something like commit history completions, which are returned by git in reverse chronological order and make no sense alphabetically (they are SHA1 hashes). See https://github.com/fish-shell/fish-shell/issues/361 for more info. --- share/completions/git.fish | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/share/completions/git.fish b/share/completions/git.fish index 6a2b92746..e1272af5b 100644 --- a/share/completions/git.fish +++ b/share/completions/git.fish @@ -427,7 +427,7 @@ complete -c git -n '__fish_git_needs_command' -a commit -d 'Record changes to th complete -c git -n '__fish_git_using_command commit' -l amend -d 'Amend the log message of the last commit' complete -f -c git -n '__fish_git_using_command commit' -a '(__fish_git_modified_files)' complete -f -c git -n '__fish_git_using_command commit' -l fixup -d 'Fixup commit to be used with rebase --autosquash' -complete -f -c git -n '__fish_git_using_command commit; and __fish_contains_opt fixup' -a '(__fish_git_recent_commits)' +complete -f -c git -n '__fish_git_using_command commit; and __fish_contains_opt fixup' -k -a '(__fish_git_recent_commits)' # TODO options ### diff