threads / patch / 53729

patchbash-completion: add git-prune into bash completion

Subject: [PATCH] bash-completion: add git-prune into bash completion

## tl;dr

4 messages between Jun 22, 2020 and Jul 10, 2020. Diffs are folded; open one to read it.

replies: 3people: 2as markdown or json

John Lin via GitGitGadget· Jun 22, 2020, 00:13 UTC · lore
From: John Lin <johnlinp@gmail.com>

Sometimes git would suggest the user to run `git prune` when there are too many unreachable loose objects. It's more user-friendly if we add git-prune into bash completion.

Signed-off-by: John Lin <johnlinp@gmail.com>
---
    bash-completion: add git-prune into bash completion
    
    Sometimes git would suggest the user to run git prune when there are too
    many unreachable loose objects. It's more user-friendly if we add
    git-prune into bash completion.
    
    Signed-off-by: John Lin johnlinp@gmail.com [johnlinp@gmail.com]
    
    Fixes #642.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-667%2Fjohnlinp%2Fadd-git-prune-bash-completion-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-667/johnlinp/add-git-prune-bash-completion-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/667
 command-list.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Show changes to command-list.txt +1 −1
diff --git a/command-list.txt b/command-list.txt
index cbb960c8436..89aa60cde7e 100644
--- a/command-list.txt
+++ b/command-list.txt
@@ -136,7 +136,7 @@ git-pack-redundant                      plumbinginterrogators
 git-pack-refs                           ancillarymanipulators
 git-parse-remote                        synchelpers
 git-patch-id                            purehelpers
-git-prune                               ancillarymanipulators
+git-prune                               ancillarymanipulators   complete
 git-prune-packed                        plumbingmanipulators
 git-pull                                mainporcelain           remote
 git-push                                mainporcelain           remote

base-commit: 101b3204f37606972b40fc17dec84560c22f69f6
-- 
gitgitgadget
Junio C Hamano· Jun 22, 2020, 18:28 UTC · re: John Lin via GitGitGadget · lore

Re: [PATCH] bash-completion: add git-prune into bash completion

"John Lin via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 5 quoted lines
> From: John Lin <johnlinp@gmail.com>
>
> Sometimes git would suggest the user to run `git prune` when there are
> too many unreachable loose objects. It's more user-friendly if we add
> git-prune into bash completion.

Yes, but it does not suggest all the time, and there is a reason. Most of the time "gc" is more appropriate, but there are narrow cases where "prune" is more appropriate and that is when the users will see suggestion to run "prune".

Isn't it too much to type p-r-u-n-e while seeing that message, typing as you read it?

I do not think it hurts to complete "git prune", in the sense that we would want to avoid completing potentially destructive operation to those who do not understand the implications, because the command is pretty much benign. But I am not sure it forces users to type too many keystrokes too frequently that it requires a tab completion. I dunno.

Will queue for now.
Thanks.
林自均· Jul 10, 2020, 01:18 UTC · re: Junio C Hamano · lore

Re: [PATCH] bash-completion: add git-prune into bash completion

Hi Junio,
I saw this integrated into master. Thanks.

Best, John Lin

Junio C Hamano <gitster@pobox.com> 於 2020年6月23日 週二 上午2:28寫道:
Show 27 quoted lines
>
> "John Lin via GitGitGadget" <gitgitgadget@gmail.com> writes:
>
> > From: John Lin <johnlinp@gmail.com>
> >
> > Sometimes git would suggest the user to run `git prune` when there are
> > too many unreachable loose objects. It's more user-friendly if we add
> > git-prune into bash completion.
>
> Yes, but it does not suggest all the time, and there is a reason.
> Most of the time "gc" is more appropriate, but there are narrow
> cases where "prune" is more appropriate and that is when the users
> will see suggestion to run "prune".
>
> Isn't it too much to type p-r-u-n-e while seeing that message,
> typing as you read it?
>
> I do not think it hurts to complete "git prune", in the sense that
> we would want to avoid completing potentially destructive operation
> to those who do not understand the implications, because the command
> is pretty much benign.  But I am not sure it forces users to type
> too many keystrokes too frequently that it requires a tab
> completion.  I dunno.
>
> Will queue for now.
>
> Thanks.
Junio C Hamano· Jul 10, 2020, 23:08 UTC · re: 林自均 · lore

Re: [PATCH] bash-completion: add git-prune into bash completion

林自均 <johnlinp@gmail.com> writes:
> Hi Junio,
>
> I saw this integrated into master. Thanks.
Thank you for writing the patch.

← back to recent threads