Re: [git-users] New user gets lost driving the Git Bash

2012-07-25 Thread Konstantin Khomoutov
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 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



Re: [git-users] New user gets lost driving the Git Bash

2012-07-25 Thread Konstantin Khomoutov
On Tue, 24 Jul 2012 13:01:32 -0700 (PDT)
Jeffery Brewer jeffery.bre...@gmail.com wrote:

 Continued thanks for all the help. I'm sorry to be so slow at
 this...I've just done very little command line operation in the past
 and probably shouldn't even be allowed near computers at all. I have
 very little experience on Linux/Unix as well, so I'm really
 floundering around in the dark here. I learned ls yesterday though,
 so I'm getting there.
 
 So when you say cmd.exe you're talking about just a normal windows 
 command line prompt?
Exactly.

 Like you go to Start and type cmd?
Yes.  No matter how you run it, cmd.exe is the process which presents
you with the regular Windows command line prompt.

 I tried that initially but only got errors (e.g. $ not recognized).
You've fell victim of a typical assumption of the authors of most
books/guides/blog posts that the reader is familiar that this symbol
denotes a command-line prompt.
While this prompt is easily tweakable in any interactive Unix-y
command-line shell (which are available in abundance, by the way), the
usage of the '$' character in the most common default setting
(including the shell found on Mac OS X). 

 Wasn't until I stumbled on the Git Bash thing that I could make Git
 work at all.
That's pretty strange.
One reason I could think of is that you did not opted for Git to be
included in your PATH when you were installing Git for Windows, so may
be when you typed git in the windows command prompt, it told you that
program is not found, was it?

 I know there are GUI's available, but I have a big desire to develop
 some command line skills and this seems like a reasonable place to
 start. I figured how to commit files yesterday! Woo hoo! All that
 seemed to go reasonably well until I did the diff command, which had
 me lost until I finally typed h and got the help screen. 
Yeah, you were interacting with the pager called less which is
ubiquitous on Unix platforms and which Git for Windows packages for
convenience (the stock pager available in Windows, called more is too
simplistic to be of any real use).
I recommend you to spend some time finding your ways in less as it's
able to do nice things like searching (via the / command),
wrapping/cutting long lines etc.

[...]

-- 
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 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



Re: [git-users] New user gets lost driving the Git Bash

2012-07-24 Thread Łukasz Siwiński
PS: The command like provided with Git for Windows is something like Bash
for Linux.

-- 
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 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



Re: [git-users] New user gets lost driving the Git Bash

2012-07-24 Thread Konstantin Khomoutov
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.

-- 
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 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



Re: [git-users] New user gets lost driving the Git Bash

2012-07-24 Thread Jeffery Brewer
Continued thanks for all the help. I'm sorry to be so slow at this...I've 
just done very little command line operation in the past and probably 
shouldn't even be allowed near computers at all. I have very little 
experience on Linux/Unix as well, so I'm really floundering around in the 
dark here. I learned ls yesterday though, so I'm getting there.

So when you say cmd.exe you're talking about just a normal windows 
command line prompt? Like you go to Start and type cmd? I tried that 
initially but only got errors (e.g. $ not recognized). Wasn't until I 
stumbled on the Git Bash thing that I could make Git work at all. 

I know there are GUI's available, but I have a big desire to develop some 
command line skills and this seems like a reasonable place to start. I 
figured how to commit files yesterday! Woo hoo! All that seemed to go 
reasonably well until I did the diff command, which had me lost until I 
finally typed h and got the help screen. 


On Tuesday, July 24, 2012 12:46:44 AM 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. 



-- 
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/-/ZTmFPr90CvoJ.
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.



Re: [git-users] New user gets lost driving the Git Bash

2012-07-24 Thread Graham Jans


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.



[git-users] New user gets lost driving the Git Bash

2012-07-23 Thread Jeffery Brewer
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.

Was able to set up my configuration settings as described in The Book. Am 
now at the beginning of Chapter 2 Installing a Repository in an Existing 
Directory and trying to figure out how to drive the Git Bash over to my 
existing directory. I tried a dir which in a normal command line gives 
you a listing of the contents of the current directory, but that's giving 
me an sh.exe: dir: command not found error. cd seems to work, so I 
tried a cd c: but not sure I've gone into the root or not. Any way to 
list files in the Git Bash?

-- 
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/-/ORaKXYZbarcJ.
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.



Re: [git-users] New user gets lost driving the Git Bash

2012-07-23 Thread Łukasz Siwiński
Ps: after:  $ echo dir alias='ls'  .bashrc exit  relaunch your
prompt (bach/command line)


2012/7/24 Łukasz Siwiński lsiwin...@gmail.com:
 do the following:

 echo alias dir =ls
 enter/

 if you want to go to c: drive do the following

 cd /c

 if you want to go to d: do the following

 cd /d

 next I recomend You git magic book (as the first position to read), it
 helped me

 practice  n'joy.

 2012/7/24 Jeffery Brewer jeffery.bre...@gmail.com:
 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.

 Was able to set up my configuration settings as described in The Book. Am
 now at the beginning of Chapter 2 Installing a Repository in an Existing
 Directory and trying to figure out how to drive the Git Bash over to my
 existing directory. I tried a dir which in a normal command line gives you
 a listing of the contents of the current directory, but that's giving me an
 sh.exe: dir: command not found error. cd seems to work, so I tried a
 cd c: but not sure I've gone into the root or not. Any way to list files
 in the Git Bash?

 --
 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/-/ORaKXYZbarcJ.
 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.



 --
 Łukasz Siwiński
 +48 504 490 537
 http://siwinski.info



-- 
Łukasz Siwiński
+48 504 490 537
http://siwinski.info

-- 
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 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



Re: [git-users] New user gets lost driving the Git Bash

2012-07-23 Thread Serge Matveenko
On Tue, Jul 24, 2012 at 3:18 AM, Łukasz Siwiński lsiwin...@gmail.com wrote:
 Ps: after:  $ echo dir alias='ls'  .bashrc exit  relaunch your
 prompt (bach/command line)

alias dir='ls -Alh'

gives more familiar look for windows user

personally I use this alias in my linux shell for over 6 years


-- 
Serge Matveenko
se...@matveenko.ru
http://www.ohloh.net/accounts/lig
http://ru.linkedin.com/in/sergematveenko

-- 
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 
git-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/git-users?hl=en.



Re: [git-users] New user gets lost driving the Git Bash

2012-07-23 Thread Jeffery Brewer
Thanks to both...

how do you move up one level in the directory structure without having to 
type the entire path? e.g. cd..

On Monday, July 23, 2012 4:30:14 PM UTC-7, Serge Matveenko wrote:

 On Tue, Jul 24, 2012 at 3:18 AM, Łukasz Siwiński lsiwin...@gmail.com 
 wrote: 
  Ps: after:  $ echo dir alias='ls'  .bashrc exit  relaunch your 
  prompt (bach/command line) 

 alias dir='ls -Alh' 

 gives more familiar look for windows user 

 personally I use this alias in my linux shell for over 6 years 


 -- 
 Serge Matveenko 
 se...@matveenko.ru 
 http://www.ohloh.net/accounts/lig 
 http://ru.linkedin.com/in/sergematveenko 


-- 
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/-/mBcY5sU4qI0J.
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.