Welcom eto learning the subtle distinctions between the *nix and *doze 
approaches.

I've no idea if the cmd window can run the prompt script (or something similar 
even) - I'm sure other more knowledgable than me can confirm that it's not the 
norm.

The normal *doze approach we all get used to is that we have a program 
'running' and then we give it commands, so we could select the git window and 
give it a command. However that's nor the way *nix (of which Git is an example 
program) work. 

In *nix (in general) a program starts, runs, and finishes (terminates) in the 
blink of an eye, e.g. ls, wc, and others, so the program stops running on 
completion. This means you have to invoke the base program any time you need 
it, and Git follow that idiom. Obviously there are some bigger programs that 
create windows and last a long time, but Git is not of that style.

For extra bonus marks have a look at articles about 'everything is a file in 
*nix' and 'files can be in memory' to give a fresh perspective. (None of them 
are right, but each is less wrong on their own terms ;-)

Personally I always run git in the bash window, just to be distinct from the 
cmd window, and then use the 'git gui', when I need that 'gui Window' long 
running app approach. But then maybe I'm odd/old.

Philip
Seasons greetings to all.
  ----- Original Message ----- 
  From: Lou Elston 
  To: Git for human beings 
  Sent: Thursday, December 24, 2015 11:28 PM
  Subject: [git-users] Re: Fairly new to GIT questions


  A related question.  As I said in my first post, I am working my way through 
the Lynda beginning GIT videos.  Just finished the part where it says that you 
can show the branch in the prompt.  On Windows, they gave a Bash example.  
Nowhere could I find a way to do this on Windows using 'GIT CMD', (as I am not 
using Bash). It appears that this cannot be done.  Anyway, I got to thinking 
about the fact that you have to begin every GIT command (GIT CMD, or Bash), 
with 'git', and I was wondering if I could just open a Windows cmd window (not 
use the 'GIT CMD' shortcut), and if GIT would work. and the answer is yes (as 
long as I start each command with 'git'.  So my question here is, is the 'GIT 
CMD' shortcut just opening a Windows cmd window, or, is this 'GIT CMD' shortcut 
actually doing something with\enabling some with, etc., etc...GIT?

  On Wednesday, December 23, 2015 at 1:03:49 PM UTC-5, Lou Elston wrote:
    I am a Windows user.  I do not know BASH, so I am using GIT-CMD, and am 
working my way through the LinkedIn\Lynda, GIT Beginners course.  Why (it does 
not happen every single time), do I have to do a Cntrl\C to get the prompt back 
(it appears to be hanging\waiting for something)?


    Also, is there any kind of test, exam, or certification for GIT?  Something 
to show that I know the basics, that I can show, and\or use to get ready for an 
interview?

  -- 
  You received this message because you are subscribed to the Google Groups 
"Git for human beings" group.
  To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected].
  For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to