![]() Git-for-windows / build-extra -cd-to-home, git-bash and git-cmd will use that as the working directory when launched, "C:\Program Files\Git\git-bash.exe" -cd-to-home Git will use the default console window of Windows ("cmd.exe"). Non-rectangular selection an a Unicode font, Windows console programs (suchĪs interactive Python) must be launched via `winpty` to work in MinTTY. Git Bash will use MinTTY as terminal emulator, which spoerts a resizable windows, (x) Une MinTTY (the default terminal of MSYS2) Configuring the terminal emulator to use with Git Bash Text file? Chossin this option is not recommended for cross-plateform Git will not perform any conversions when checking out or commiting This is the recommended sestting on Unix ("tocrlf" is set to "input"). WhenĬommitting text files, CRLF will be converted to LF. Git will not perform any conversoin when checking out text files. ![]() ( ) Checkout as-is, commit Unix-style endings This the recommended setting on Windows ("tocrlf" is set to "true"). Texte files, CRLF will be converted to LF. ![]() Git convert LF to CRLF when checkin out text files. (x) Checkout Windows-style, commint Unix-style line ending ![]() If you want to show this too (which I recommend for clarity), then you also need to fill out the "Icon" field.- Configuring the line ending conversions 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)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |