Thread (3 messages) flat view 3 messages, 3 authors, 2016-06-15

Re: [RFC PATCH 2/2] Teach git-blame --gui how to start git-gui blame

From: Shawn O. Pearce <hidden>
Date: 2016-06-15 22:43:17

Junio C Hamano [off-list ref] wrote:
"Shawn O. Pearce" [off-list ref] writes:
quoted
Junio C Hamano [off-list ref] wrote:
quoted
This is only minor nuisance, but can we do something about this?

 $ git gui --version
 Application initialization failed: no display name and no $DISPLAY environment variable

I know it is from wish, not you, so I wouldn't insist, though.
If this makes life any harder to people on Windows, especially
minGW, I would suggest against it.
Its already done.  I don't think it will make a difference either
way right now.

Currently we still have to have a Bourne shell on both Cygwin
and MINGW platforms to perform key actions, like say git-clone.
The startup cost of git-gui is also rather high there anyway, so
this extra if test in Bourne shell before we exec into Tcl isn't
going to kill us.

Besides, you can side-step the entire Bourne shell thing by just
starting git-gui in wish yourself.  E.g.

  CALL /path/to/wish.exe /path/to/git-gui -- ...


I'd like to come back and make git-gui easier to install, perhaps by
making "starpacks" of git-gui and Git plumbing available for some
popular systems (e.g. MINGW/Windows, Mac OS X).  Such starpacks
would give users an easy way to get git-gui (and thus basic Git)
up and running quickly.  At that point I will need to revisit this
bootstrap code anyway.

-- 
Shawn.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help