ekocros.blogg.se

1. #Git bash windows 10 ctrl c not working upgrade#
2. #Git bash windows 10 ctrl c not working full#
3. #Git bash windows 10 ctrl c not working windows#

#Git bash windows 10 ctrl c not working windows#

For Linux, Ctrl+C would work mostly as expected however on Windows Ctrl+C mostly doesnt work especially if Python is running blocking call such as thread. If you want to show this too (which I recommend for clarity), then you also need to fill out the "Icon" field. It turns out that as of Python 3.6, the Python interpreter handles Ctrl+C differently for Linux and Windows. This looks great! Only thing missing is the "icon" for Git-Bash. It didn't take me very long to figure out that the correct exe that needs to be referenced is this one: C:\Program Files\Git\bin\bash.exe (This one is in a subdirectory of the initial one and does, to my knowledge, the same)Īfter hitting save, you can try opening the git-bash tab again and if everything was done well, then you should see the result as shown below: After looking around for a bit, I discovered that there is also another set of exe's sitting in the folders next to the one containing git-bash.exe. Then, what you need to do, is open the VSCode settings, add a profile and fill out the fields (We'll first focus on the name for the profile and the path that we just found):Īfter that, we just have to validate our new profile by opening a new tab by clicking on the "downward pointing arrow" and and then on the newly created "Git-Bash" profile:Īs you can see, the behavior is not at all what we expect as Git-Bash opens in a new window instead of a new tab! This is strange, but not a huge problem. In my case, but almost always this value is C:\Program Files\Git\git-bash.exe (so you can save yourself the trouble work with this one)

#Git bash windows 10 ctrl c not working full#

in the properties window that opens, you can find the full path to the Git-Bash exe in the field with name "target":.

I now have to run python -i for the interactive python. Among a couple of other unexpected changes from my earlier setup using a previous version of Git Bash and mostly running Python 3.9 (i.e. I just downloaded the latest Git Bash (2.36.1 64-bit) and installed Python 10.

In the popup that opens, click on properties: Ctrl+Z does not exit Python 3.10 in Git Bash. Right click the Git-Bash icon in the taskbar and then right click again on Git-Bash in the menu that shows: After that I'll show the correct approach!įinding the path to the Git-Bash exe can be done in 3 simple steps: The idea is that I first found a suboptimal solution (out of a naive approach), which I'll explain first.

I discovered pretty quick that there was a catch and in this post, I want to show you what I did, why it didn't work and finally, how you need to approach this.Īll you need, or so I thought, is to add the exe of Gi-Bash to a new windows terminal profile. At that moment, I didn't realize that this would result in a blogpost 😉. A global configuration in /. 2.35.3) and disable interactive prompt ( docs ): git config -global credential.interactive false.

#Git bash windows 10 ctrl c not working upgrade#

The fix was to upgrade git to +v2.30.z (i.e. and I immediately showed him how this can be done via the settings of Windows terminal. In my case, I had this issue in relation to the federated authentication to AWS CodeCommit. First thing he asked then, was if it would be possible to add Git-Bash as a tab. This morning I saw a colleague working in Git-Bash and the good-old-fashioned "windows command line" and I thought to myself, why doesn't he "just" use Windows terminal? So, I showed him Windows Terminal and he was impressed.