Hi Christopher, I (personally) am also trying to get my head around the terminal awkwardness. Have a look at
https://groups.google.com/forum/#!msg/git-for-windows/o4vIpvIEWhE/pbp9-dHqBgAJ https://github.com/git-for-windows/git/issues/1674 https://github.com/git-for-windows/git/pull/2357?email_source=notifications&email_token=AAG7HJ555OM6DJGKTQ54OVLQPITQ7A5CNFSM4JBMC7D2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBWCQ4Q#issuecomment-543959154 (some cross linkage and links to other GH Issues) IIUC the git-bash is compiled as a resource from the build-extra makefile and links into the git.cmd (I think). plus, it updates the path so that the current git can be found. Dscho is the expert on this. I'm trying to document some of the intricacies that folk may need to know - so my ignorance is both a help and a hindrance :wink: Philip On Sunday, October 20, 2019 at 2:39:03 PM UTC+1, CrestChristopher wrote: > > Hi, I’m having an issue with git-bash; and I hope someone can help. > > When I’m in command (DOS) in Windows, I can change between DOS and > Powershell by simply typing in either cmd or powershell and my shell > changes. Since I’m using another terminal, rather then the default Windows > command shell this terminal has an option which I can include paths for > whatever shell I choose, unfortunately when I include the path to git-bash > and type git-bash in the terminal, rather then it changing to *git-bash*, > I get an error; it is unrecognized ? > > How can I make this work, must I give the path to a .bashrc file or > .bash_profile file ? > > > Christopher > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/2b05d706-0cab-4da7-88d2-458feaebe922%40googlegroups.com.
