Re: Git Bash Bug

Hi Paul, On Fri, 14 Jul 2017, Paul Smith wrote: > On Fri, 2017-07-14 at 22:33 +0200, Johannes Schindelin wrote: > > > You absolutely have to have /bin and /usr/bin on your PATH, > > > > As Kavita talks about Git Bash, it is probably Git for Windows, for > > which /bin should not be in the PATH

Re: Git Bash Bug

On Fri, 2017-07-14 at 22:33 +0200, Johannes Schindelin wrote: > > You absolutely have to have /bin and /usr/bin on your PATH, > > As Kavita talks about Git Bash, it is probably Git for Windows, for > which /bin should not be in the PATH but /mingw64/bin or /mingw32/bin > (depending on the

Re: Git Bash Bug

Hi, On Fri, 14 Jul 2017, Paul Smith wrote: > On Fri, 2017-07-14 at 09:59 -0500, Kavita Desai wrote: > > What does "echo $PATH" show? > > /c/Users/Kavita/ > > Well, there you go. That's clearly wrong. > > You absolutely have to have /bin and /usr/bin on your PATH, As Kavita talks about Git

Re: Git Bash Bug

On Fri, 2017-07-14 at 09:59 -0500, Kavita Desai wrote: > What does "echo $PATH" show? > /c/Users/Kavita/ Well, there you go. That's clearly wrong. You absolutely have to have /bin and /usr/bin on your PATH, _at least_ if you want to be able to run standard UNIX tools. And most likely you'll

Re: Git Bash Bug

Here are the results. What does "echo $PATH" show? /c/Users/Kavita/ What does "type -a ls" show? ls is aliased to `ls -F --color=auto --show-control-chars' On Fri, Jul 14, 2017 at 9:37 AM, Paul Smith wrote: > On Fri, 2017-07-14 at 09:34 -0500, Kavita Desai wrote: >>

Re: Git Bash Bug

On Fri, 2017-07-14 at 09:34 -0500, Kavita Desai wrote: > Sorry for not being specific. What I meant by not working was that the > bash commands are not found. > Here is an example > > $ ls > bash: ls: command not found The most obvious issue is your PATH is wrong. What does "echo $PATH" show?

Re: Git Bash Bug

Sorry for not being specific. What I meant by not working was that the bash commands are not found. Here is an example $ ls bash: ls: command not found Kavita On Fri, Jul 14, 2017 at 9:28 AM, Johannes Schindelin wrote: > Hi Kavita, > > On Fri, 14 Jul 2017, Kavita

Re: Git Bash Bug

Hi Kavita, On Fri, 14 Jul 2017, Kavita Desai wrote: > Originally, when I first had Git Bash everything was working > perfectly. Randomly one day, my bash commands were not working. There are a gazillion ways how commands can "not work". You *need* to be more specific here. In the least, a

Git Bash Bug

Hello, Originally, when I first had Git Bash everything was working perfectly. Randomly one day, my bash commands were not working. I uninstalled Git Bash an reinstalled it. I have been trying for 3 weeks to get it to work again. I am working on Windows 10. I have tried editing the PATH

git bash bug: ipython doesn't work

I downloaded git for windows v2.5.1. And in git bash I can't launch ipython. I suppose it forwards stdout somethere. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at

Re: git bash bug: ipython doesn't work

Hi Sergey, On 2015-09-03 18:56, Sergey Chipiga wrote: > I downloaded git for windows v2.5.1. And in git bash I can't launch ipython. > I suppose it forwards stdout somethere. I replied in the ticket you opened on GitHub: https://github.com/git-for-windows/git/issues/352 Ciao, Johannes -- To