git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 6/9] update 'git-rm' bash completion according to the man page

From
ETEmmanuel Trillaud <etrillaud@gmail.com>
Date
Aug 8, 2009, 20:33 UTC
Message-ID
<20090808223312.75ba3d10@eleanor>
In-Reply-To
<7vljludr2d.fsf@alter.siamese.dyndns.org>
Show 7 quoted lines
> > -		__gitcomp "--cached --dry-run --ignore-unmatch
> > --quiet"
> > +		__gitcomp "--force --cached --dry-run
> > --ignore-unmatch --quiet"
> 
> I thought not completing --force to allow a dangerous operation was a
> conscious decision.

For me, completion as always been a reminder for options I forgot (or I think they exist) and I use short options when I know them because it is easier to type. So IMHO '--force' is a useful option that deserve to be complete.

But if you make a conscious decision in the past to not complete '--force', I won't fight :-) and I will just add a comment in the git-completion script for the guys like me who think it is missing.

Best regard 
Emmanuel
Previous: Junio C Hamano
Message 3 of 3 in “update 'git-rm' bash completion according to the man page”
  1. 6/9 update 'git-rm' bash completion according to the man pageEmmanuel Trillaud, Aug 8, 2009
  2. Junio C HamanoAug 8, 2009
  3. Emmanuel TrillaudAug 8, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.