Re: Starting from a Windows Command Prompt

2017-07-12 Thread Brian Inglis
On 2017-07-12 14:15, Andrey Repin wrote: > Brian Inglis wrote: >> On 2017-07-12 00:16, Ugly Leper wrote: >>> Starting from a Windows Command Prompt, and using a syntax recommended >>> from years ago I still start a bash shell with >>> start /wait bin\bash (i.e.

Re: Starting from a Windows Command Prompt

2017-07-12 Thread Andrey Repin
Greetings, Brian Inglis! > On 2017-07-12 00:16, Ugly Leper wrote: >> Starting from a Windows Command Prompt, and using a syntax recommended >> from years ago I still start a bash shell with >> start /wait bin\bash (i.e. not just bin\bash) >> and a mintty shell with &g

Re: Starting from a Windows Command Prompt

2017-07-12 Thread Brian Inglis
On 2017-07-12 00:16, Ugly Leper wrote: > Starting from a Windows Command Prompt, and using a syntax recommended > from years ago I still start a bash shell with > start /wait bin\bash (i.e. not just bin\bash) > and a mintty shell with > start bin\mintty (i.e. not just bin\mi

Re: Starting from a Windows Command Prompt

2017-07-12 Thread Andrey Repin
Greetings, Ugly Leper! > Starting from a Windows Command Prompt, and using a syntax recommended > from years ago I still start a bash shell with > start /wait bin\bash (i.e. not just bin\bash) > and a mintty shell with mintty is not a shell, it's a terminal emulator. > s

Starting from a Windows Command Prompt

2017-07-11 Thread Ugly Leper
Starting from a Windows Command Prompt, and using a syntax recommended from years ago I still start a bash shell with start /wait bin\bash (i.e. not just bin\bash) and a mintty shell with start bin\mintty (i.e. not just bin\mintty) and yet experiment shows that both simplified forms in brackets