{"thread":{"id":"46385","subject":"Git Bash Bug","startedAt":"2017-07-14T13:43:27Z","lastAt":"2017-07-14T21:53:06Z","messageCount":9,"participants":["Kavita Desai","Johannes Schindelin","Paul Smith"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"324506","messageId":"CAAu0pLedy5xqUgF7drMf=tQgMJD4rXq+JvKaiE54EdRFZWuTkQ@mail.gmail.com","threadId":"46385","inReplyTo":null,"subject":"Git Bash Bug","fromName":"Kavita Desai","fromEmail":"kvdesai2@illinois.edu","sentAt":"2017-07-14T13:43:20Z","receivedAt":"2017-07-14T13:43:27Z","isPatch":false,"sender":{"key":"kvdesai2@illinois.edu","avatar":null},"body":"Hello,\n\nOriginally, when I first had Git Bash everything was working\nperfectly. Randomly one day, my bash commands were not working. I\nuninstalled Git Bash an reinstalled it. I have been trying for 3 weeks\nto get it to work again. I am working on Windows 10.  I have tried\nediting the PATH variables and the PATH environment variables and\nnothing seems to be working. Do you have any other suggestions?\n\n\n\nThank you,\n\nKavita\n"},{"id":"324509","messageId":"alpine.DEB.2.21.1.1707141625150.4193@virtualbox","threadId":"46385","inReplyTo":"CAAu0pLedy5xqUgF7drMf=tQgMJD4rXq+JvKaiE54EdRFZWuTkQ@mail.gmail.com","subject":"Re: Git Bash Bug","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2017-07-14T14:28:40Z","receivedAt":"2017-07-14T14:28:52Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Kavita,\n\nOn Fri, 14 Jul 2017, Kavita Desai wrote:\n\n> Originally, when I first had Git Bash everything was working\n> perfectly. Randomly one day, my bash commands were not working.\n\nThere are a gazillion ways how commands can \"not work\". You *need* to be\nmore specific here. In the least, a precise pasted output of a failed\ncommand is necessary.\n\nIn addition, a couple of other points of interest would be good to know,\nthe issue reporting template at\nhttps://github.com/git-for-windows/git/issues/new tries to help you\nprovide as much important information as you can. Maybe give it a try?\n\nCiao,\nJohannes\n"},{"id":"324510","messageId":"CAAu0pLdmGc_kq_w0Fm6W4XDqOe=iKSyAyLct+yH6y+7FPUHtnA@mail.gmail.com","threadId":"46385","inReplyTo":"alpine.DEB.2.21.1.1707141625150.4193@virtualbox","subject":"Re: Git Bash Bug","fromName":"Kavita Desai","fromEmail":"kvdesai2@illinois.edu","sentAt":"2017-07-14T14:34:02Z","receivedAt":"2017-07-14T14:34:29Z","isPatch":false,"sender":{"key":"kvdesai2@illinois.edu","avatar":null},"body":"Sorry for not being specific. What I meant by not working was that the\nbash commands are not found.\nHere is an example\n\n$ ls\nbash: ls: command not found\n\nKavita\n\nOn Fri, Jul 14, 2017 at 9:28 AM, Johannes Schindelin\n<Johannes.Schindelin@gmx.de> wrote:\n> Hi Kavita,\n>\n> On Fri, 14 Jul 2017, Kavita Desai wrote:\n>\n>> Originally, when I first had Git Bash everything was working\n>> perfectly. Randomly one day, my bash commands were not working.\n>\n> There are a gazillion ways how commands can \"not work\". You *need* to be\n> more specific here. In the least, a precise pasted output of a failed\n> command is necessary.\n>\n> In addition, a couple of other points of interest would be good to know,\n> the issue reporting template at\n> https://github.com/git-for-windows/git/issues/new tries to help you\n> provide as much important information as you can. Maybe give it a try?\n>\n> Ciao,\n> Johannes\n\n\n\n-- \nKavita Desai\nUIUC Engineering Physics 2018\nEngineering Outreach Society Engineering Open House Chair\nUIUC Housing Ike. South Front Desk Clerk\n"},{"id":"324512","messageId":"1500043024.25789.105.camel@mad-scientist.net","threadId":"46385","inReplyTo":"CAAu0pLdmGc_kq_w0Fm6W4XDqOe=iKSyAyLct+yH6y+7FPUHtnA@mail.gmail.com","subject":"Re: Git Bash Bug","fromName":"Paul Smith","fromEmail":"paul@mad-scientist.net","sentAt":"2017-07-14T14:37:04Z","receivedAt":"2017-07-14T14:37:14Z","isPatch":false,"sender":{"key":"paul@mad-scientist.net","avatar":"https://avatars.githubusercontent.com/u/109636?v=4"},"body":"On Fri, 2017-07-14 at 09:34 -0500, Kavita Desai wrote:\n> Sorry for not being specific. What I meant by not working was that the\n> bash commands are not found.\n> Here is an example\n> \n> $ ls\n> bash: ls: command not found\n\nThe most obvious issue is your PATH is wrong.\n\nWhat does \"echo $PATH\" show?\n\nWhat does \"type -a ls\" show?\n"},{"id":"324525","messageId":"CAAu0pLdjvcxda0rip8JOzt1q0HNuu4dBNHvEzJbeey6yRSyCCQ@mail.gmail.com","threadId":"46385","inReplyTo":"1500043024.25789.105.camel@mad-scientist.net","subject":"Re: Git Bash Bug","fromName":"Kavita Desai","fromEmail":"kvdesai2@illinois.edu","sentAt":"2017-07-14T14:59:16Z","receivedAt":"2017-07-14T14:59:24Z","isPatch":false,"sender":{"key":"kvdesai2@illinois.edu","avatar":null},"body":"Here are the results.\n\nWhat does \"echo $PATH\" show?\n/c/Users/Kavita/\n\nWhat does \"type -a ls\" show?\nls is aliased to `ls -F --color=auto --show-control-chars'\n\n\n\nOn Fri, Jul 14, 2017 at 9:37 AM, Paul Smith <paul@mad-scientist.net> wrote:\n> On Fri, 2017-07-14 at 09:34 -0500, Kavita Desai wrote:\n>> Sorry for not being specific. What I meant by not working was that the\n>> bash commands are not found.\n>> Here is an example\n>>\n>> $ ls\n>> bash: ls: command not found\n>\n> The most obvious issue is your PATH is wrong.\n>\n> What does \"echo $PATH\" show?\n>\n> What does \"type -a ls\" show?\n\n\n\n-- \nKavita Desai\nUIUC Engineering Physics 2018\nEngineering Outreach Society Engineering Open House Chair\nUIUC Housing Ike. South Front Desk Clerk\n"},{"id":"324527","messageId":"1500044588.25789.109.camel@mad-scientist.net","threadId":"46385","inReplyTo":"CAAu0pLdjvcxda0rip8JOzt1q0HNuu4dBNHvEzJbeey6yRSyCCQ@mail.gmail.com","subject":"Re: Git Bash Bug","fromName":"Paul Smith","fromEmail":"paul@mad-scientist.net","sentAt":"2017-07-14T15:03:08Z","receivedAt":"2017-07-14T15:15:42Z","isPatch":false,"sender":{"key":"paul@mad-scientist.net","avatar":"https://avatars.githubusercontent.com/u/109636?v=4"},"body":"On Fri, 2017-07-14 at 09:59 -0500, Kavita Desai wrote:\n> What does \"echo $PATH\" show?\n> /c/Users/Kavita/\n\nWell, there you go.  That's clearly wrong.\n\nYou absolutely have to have /bin and /usr/bin on your PATH, _at least_\nif you want to be able to run standard UNIX tools.  And most likely\nyou'll have a ton of other directories on your PATH as well.\n\nI would investigate the shell configuration files etc. and see where\nyou've messed up resetting your PATH variable.\n\n> What does \"type -a ls\" show?\n> ls is aliased to `ls -F --color=auto --show-control-chars'\n\nYep.  There is no ls binary found.\n"},{"id":"324552","messageId":"alpine.DEB.2.21.1.1707142227240.4193@virtualbox","threadId":"46385","inReplyTo":"1500044588.25789.109.camel@mad-scientist.net","subject":"Re: Git Bash Bug","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2017-07-14T20:33:04Z","receivedAt":"2017-07-14T20:33:19Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Fri, 14 Jul 2017, Paul Smith wrote:\n\n> On Fri, 2017-07-14 at 09:59 -0500, Kavita Desai wrote:\n> > What does \"echo $PATH\" show?\n> > /c/Users/Kavita/\n> \n> Well, there you go.  That's clearly wrong.\n> \n> You absolutely have to have /bin and /usr/bin on your PATH,\n\nAs Kavita talks about Git Bash, it is probably Git for Windows, for which\n/bin should not be in the PATH but /mingw64/bin or /mingw32/bin (depending\non the architecture).\n\nIt may be messed up by some strange setting in the User Environment. Go to\nthe Windows Explorer, right-click on \"This PC\", select \"Properties\", in\nthe newly-opened window (\"Control Panel>All Control Panel Items>System\"),\nnext to the \"Computer name, domain, and workgroup settings\" select \"Change\nsettings\" which brings up the \"System Properties\" window, in whose\n\"Advanced\" tab is an \"Environment Variables\" button.\n\n(Or hit the Windows key, type \"Edit the system environment variables\")\n\nYou should find the \"Path\" variable at least in the System variables. It\nis case-insensitive, so if your User variables contain, say, an empty\nvalue for a key \"paTH\", then the riddle is solved.\n\nCiao,\nJohannes\n"},{"id":"324554","messageId":"1500066765.25789.111.camel@mad-scientist.net","threadId":"46385","inReplyTo":"alpine.DEB.2.21.1.1707142227240.4193@virtualbox","subject":"Re: Git Bash Bug","fromName":"Paul Smith","fromEmail":"paul@mad-scientist.net","sentAt":"2017-07-14T21:12:45Z","receivedAt":"2017-07-14T21:12:55Z","isPatch":false,"sender":{"key":"paul@mad-scientist.net","avatar":"https://avatars.githubusercontent.com/u/109636?v=4"},"body":"On Fri, 2017-07-14 at 22:33 +0200, Johannes Schindelin wrote:\n> > You absolutely have to have /bin and /usr/bin on your PATH,\n> \n> As Kavita talks about Git Bash, it is probably Git for Windows, for\n> which /bin should not be in the PATH but /mingw64/bin or /mingw32/bin\n> (depending on the architecture).\n\nI did check this with my Git for Windows installation before posting. \nMine is older (2.7.0) though so maybe things have changed:\n\n  pds@build-win MINGW64 ~\n  $ type -a ls\n  ls is aliased to `ls -F --color=auto --show-control-chars'\n  ls is /usr/bin/ls\n  ls is /bin/ls\n  ls is /usr/bin/ls\n  ls is /usr/bin/ls\n\nClearly I have a lot of duplicates on my PATH now that I notice :)\n\nI have /mingw64/bin on my PATH as well but looking there it has git,\ngettext, edit, a bunch of DLL's, etc. but it doesn't contain ls or\nother coreutils programs.\n\nCheers!\n"},{"id":"324556","messageId":"alpine.DEB.2.21.1.1707142345050.4193@virtualbox","threadId":"46385","inReplyTo":"1500066765.25789.111.camel@mad-scientist.net","subject":"Re: Git Bash Bug","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2017-07-14T21:52:54Z","receivedAt":"2017-07-14T21:53:06Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi Paul,\n\nOn Fri, 14 Jul 2017, Paul Smith wrote:\n\n> On Fri, 2017-07-14 at 22:33 +0200, Johannes Schindelin wrote:\n> > > You absolutely have to have /bin and /usr/bin on your PATH,\n> > \n> > As Kavita talks about Git Bash, it is probably Git for Windows, for\n> > which /bin should not be in the PATH but /mingw64/bin or /mingw32/bin\n> > (depending on the architecture).\n> \n> I did check this with my Git for Windows installation before posting. \n> Mine is older (2.7.0) though so maybe things have changed:\n> \n>   pds@build-win MINGW64 ~\n>   $ type -a ls\n>   ls is aliased to `ls -F --color=auto --show-control-chars'\n>   ls is /usr/bin/ls\n>   ls is /bin/ls\n>   ls is /usr/bin/ls\n>   ls is /usr/bin/ls\n\nOh wow ;-)\n\nFor the record, /bin/ is simply mapped to /usr/bin/. They are not\ndifferent directories, really.\n\n> Clearly I have a lot of duplicates on my PATH now that I notice :)\n\n;-)\n\n> I have /mingw64/bin on my PATH as well but looking there it has git,\n> gettext, edit, a bunch of DLL's, etc. but it doesn't contain ls or\n> other coreutils programs.\n\nRight. The difference between executables in /mingw64/bin/ and in\n/usr/bin/ is that the latter executables all implicitly link to\nmsys-2.0.dll, i.e. the POSIX emulation layer based on Cygwin. As you\nprobably guessed: the coreutils are all compiled using that POSIX\nemulation layer.\n\nCiao,\nJohannes\n"}]}