304737 – Git bash-completion errors on non-gitlized directory.

Bug 304737 - Git bash-completion errors on non-gitlized directory.

Summary: Git bash-completion errors on non-gitlized directory.

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Development (show other bugs)
Hardware:	All Linux

Importance:	High major (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-02-12 16:16 UTC by Cheng
Modified:	2010-03-23 19:39 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Cheng 2010-02-12 16:16:44 UTC

On a directory without git enabled, git bash-completion has a fatal error message.



Reproducible: Always

Steps to Reproduce:
1. Enable git bashcomp
2. Type `git <tab>`

Actual Results:  
# git <tab>fatal: error processing config file(s)
fatal: error processing config file(s)

add                 commit              init                request-pull 
am                  config              instaweb            reset 
... ...

Expected Results:  
No fatal error should happen here.

Comment 1 Thomas Sachau gentoo-dev

2010-03-12 14:13:50 UTC

Please attache your emerge --info and emerge -pv git

Comment 2 Cheng 2010-03-15 06:10:15 UTC

I've found the error is caused by the absent of ~/.gitconfig.

That machine is currently unavailable, so I can't provider further infos for now.


(In reply to comment #1)
> Please attache your emerge --info and emerge -pv git
>

Comment 3 Ben de Groot (RETIRED) gentoo-dev

2010-03-23 19:39:28 UTC

From what I understand this is not a bug, but expected behavior. You could file a bug upstream with the git developers to provide a more meaningful error message maybe.