On Thu, Dec 24, 2015 at 7:30 AM, Konstantin Khomoutov <
flatw...@users.sourceforge.net> wrote:

> On Wed, 23 Dec 2015 10:03:49 -0800 (PST)
> Lou Elston <louelston...@gmail.com> 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)?

I don't know what this git command is. Why not just load up Cygwin? That
has full bash and git support.

> A guess: you run some command, it outputs something to you and then
> shows the ':' character in the lower left corner of your console window
> (usually with a blinking cursor right beside it as well).
> Is this the case?
> If yes, this is the so-called "pager" presenting you the output of the
> Git command you have run, and unless you took special measures to
> override this, the pager Git uses by default is named "less" and is
> bundled with Git for Windows.  Git tries to be smart so, again, unless
> overridden or told not to in a particular command invocation, it sees
> if the prospective output will fit into whatever number of text lines
> your console window shows, and if it sees the output will be larger
> than that it spawns the pages automatically and pipes the output to it.
> That explains why you see the pager when doing `git log --patch`
> but don't see it when doing `git log -2`.
> The "less" program [1] allows you to scroll up and down (cursor keys,
> page up/page down keys), search through whatever it displays ('/' or '?'),
> place anchors (and jump to them) etc.  To quit from it just press 'q'
> (for "quit").  To get built-in help, type 'h' ('q' exits from this mode).
> Google for less+pager+manual if you want to know more.
> You can start with [1].
> > 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?

I don't know about the people you deal with, but I've been involved in
hiring dozens of people. I never
really look at any certificates etc.

IMHO the best approach is to use git for your work as much as you can. Get
yourself a free account on github
and store files there.

git alone is unlikely to get you a job, so do some programming and store
the files there. You can then steer the interviewer to your github
repositories to show examples of your work as well as proving you've used
git for your projects.

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 git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to