On Tue, 24 Jul 2012 14:38:19 -0700 (PDT)
Graham Jans <graham.j...@gmail.com> wrote:

>> 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.
This is indeed a valid point.
But this is an advanced technique which is not really needed to just
use Git or get started with it.

> 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.
Because most people don't really need that.
Having only git front-end script (git.cmd) in the PATH is sufficient
for usual workflows.

> As well, the coloring doesn't work for me in cmd.exe.
Coloring does work OK for me after setting the core.ui configuration
variable to "auto".  Both in the command prompt and in the built-in
pager (less).

> So all in all I recommend using Git Bash at least for learning.
I tend to disagree: using a unix-y shell in a Windows environment does
have rough edges; if a person has little experience with command-line
(I think he stated exactly this), I'd say it's better to learn native
tools first.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com.
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to