On Tuesday, 24 July 2012 00:46:44 UTC-7, Konstantin Khomoutov wrote:
>
> On Mon, Jul 23, 2012 at 04:13:50PM -0700, Jeffery Brewer wrote: 
> > Aha! Figured out that after installing on windows you don't go to a 
> command 
> > line directly, you have to go through "Start > All Programs > Git > Git 
> > Bash" which gives you a different kind of command line. 
> [...] 
>
> Note that you don't *have to* use Git bash: everything just works in the 
> regular cmd.exe.  Actually, the existence of Git bash is due to some 
> parts of Git are written as Unix shell scripts so Git for Windows has to 
> ship with a shell implementing POSIX semantics. 
>
> There's no consensus in the Git for Windows community on what shell to 
> use for interactive work with Git.  I, for one, prefer cmd.exe as I tend 
> to use the shell not only for Git. 
>
>
As Konstantin says, there's no consensus. However, I recommend using Git 
Bash, as it makes utilizing small script snippets etc. that you find around 
the net more accessible (because you don't have to "translate" them to 
windows-style, can just use them in the unix-style presented.

As well, getting the various bits of Git Bash to work in cmd.exe requires 
choosing the correct options when installing; the installer has a big red 
warning here so most people choose not to do that.

As well, the coloring doesn't work for me in cmd.exe. So all in all I 
recommend using Git Bash at least for learning.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/git-users/-/cf-PGK6z3AUJ.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.

Reply via email to