DEV Community: yumetodo

Make the integrated shell of Visual Studio Code to bash of MSYS2

yumetodo — Tue, 22 May 2018 12:23:56 +0000

Notice

This article is a translation of the post written in Japanese below:

Visual Studio Code 15.1の統合シェルをMSYS2のbashにする - Qiita

Target Visual Studio Code version

15.1 or later

Previous research

First of all, when you google about this story, the story that uses git of msys2 gets mixed, there is no googleability.

Well, first of all, you can find this post:

Visual Studio CodeのIntegrated Terminalでmsys2のzshを使う - 備忘録β版
http://yami-beta.hateblo.jp/entry/2016/06/08/000000

Then, there is such information below:

mattnさんによる実行モジュールがあるようなので、そちらを用いると良さそうです。（コメント欄参照）
(en)There seems to be an execution module by mattn, so it seems good to use it. (See comment field)
Visual Studio Code で msys2 の bash を使う方法 · GitHub

So, I watch that:

go でbash-login.goをビルドした後、出来上がったexeを以下の様に指定する。
(en)After buildin bash-login.go with go, specify the completed exe as follows.

Well... build with go ...? I feel lazy even if I need to build only once.

While watching as if there is any other information,

Visual Studio Codeの統合シェルをMSYS2のBashにしたら.bash_profileが読み込まれなかった - Qiita
http://qiita.com/catfist/items/ea925fb9e0ba5c0ba9f3

Although it can be found. However, they says:

Do not open workspace as working directory

Moreover, it is ridiculous to use VSCode extension to resolve it. WTF!

The way to make the integrated shell of Visual Studio Code to bash of MSYS2

Write below in setting.json:

{
    "terminal.integrated.shell.windows": "C:\\msys64\\usr\\bin\\bash.exe",
    "terminal.integrated.env.windows": {
        "MSYSTEM": "MINGW64",
        "CHERE_INVOKING": "1"
    },
    "terminal.integrated.shellArgs.windows": [
        "--login"
    ],
    "terminal.integrated.cursorStyle": "line"
}

terminal.integrated.cursorStyle is optional.

explanation

`terminal.integrated.shell.windows`

Specify full-path for bash. Be careful not to specify the bash not part of msys2(ex. the bash of git-bash).

`terminal.integrated.env.windows`

You can set environmental variable when create process.

`MSYSTEM`

Every MSYS2 user will know that MSYS2 has 3 mode, MSYS, MINGW32, MINGW64, and $PATH is also(/usr/bin, /mingw32/bin, /mingw64/bin).

MSYS is almost only for creating msys2 package.

MINGW32 is based on the gcc that exception model is dwarf, not SEH, due to patent of Borland, for i686.

MINGW64 is main environmental.

`CHERE_INVOKING`

For flags that decide whether to set the working directory to the path of environment variable $HOME when logging in to bash, setting it to 1 prevents movement.

In the post below:
Visual Studio Codeの統合シェルをMSYS2のBashにしたら.bash_profileが読み込まれなかった - Qiita
http://qiita.com/catfist/items/ea925fb9e0ba5c0ba9f3
they says that cannot open workspace directory as current directory. The reason is they forget to set this flag. No VSCode extension is required like @catfist

Well, msys2_shell.cmd's code is too unreadable, so it's unavoidable if they did not understand.

ref:

Cygwin導入＆ある程度日本語化（Cygwin-JE未使用）｜mizuk6nの【公開備忘録】

`terminal.integrated.shellArgs.windows`

Passing --login, -l will same effect.

Now, let's read man bash.

BASH(1)                                                      General Commands Manual                                                     BASH(1)

NAME
       bash - GNU Bourne-Again SHell
OPTIONS
       -l        Make bash act as if it had been invoked as a login shell (see INVOCATION below).

       --login
              Equivalent to -l.

       --noprofile
              Do  not  read  either  the  system-wide  startup  file  /etc/profile  or any of the personal initialization files ~/.bash_profile,
              ~/.bash_login, or ~/.profile.  By default, bash reads these files when it is invoked as a login shell (see INVOCATION below).

see INVOCATION below

Please read it yourself.

To summarize, if you do not pass -l or --login, ~/.Bash_profile will not be loaded.

More detail, That is about login shell and interactive shell. Please see below:

`terminal.integrated.cursorStyle`

optional.

Specify the style of cursor of terminal. The default is "block". I like line-style so that specify "line".

Result

List of _MSC_VER and _MSC_FULL_VER

yumetodo — Tue, 22 May 2018 09:54:22 +0000

Provision of information

I'm waiting for provision of information. I will reflect as soon as possible if you write comments.

Note: Japanese version

You can see Japanese version below:

Visual Studio version and discrimination macros

Abbreviation	Product name [Visual Studio version] ^†1	VC ++ version ^†2	`_MSC_VER`	`_MSC_FULL_VER`
2022 Update 13	Visual Studio 2022 Version 17.13.0	14.43	1943	194334808
2022 Update 12	Visual Studio 2022 Version 17.12.4	14.42	1942	194234436
2022 Update 12	Visual Studio 2022 Version 17.12.3	14.42	1942	194234435
2022 Update 11	Visual Studio 2022 Version 17.11.0	14.41	1941	194134120
2022 Update 10	Visual Studio 2022 Version 17.10.5	14.40	1939	194033811
2022 Update 9	Visual Studio 2022 Version 17.9.2	14.39	1939	193933521
2022 Update 8	Visual Studio 2022 Version 17.8.3	14.38	1938	193833133
2022 Update 7	Visual Studio 2022 Version 17.7.0	14.37	1937	193732822
2022 Update 6	Visual Studio 2022 Version 17.6.2	14.36	1936	193632532
2022 Update 5	Visual Studio 2022 Version 17.5.4	??	1935	193532217
2022 Update 4	Visual Studio 2022 Version 17.4.9	??	1934	193431944
2022 Update 3	Visual Studio 2022 Version 17.3.6	14.33	1933	193331630
2022 Update 2	Visual Studio 2022 Version 17.2.2	14.32	1932	193231329
2022	Visual Studio 2022 Version 17.0.2	14.30	1930	193030706
2022	Visual Studio 2022 Version 17.0.1	14.30	1930	193030705
2019 Update 11	Visual Studio 2019 version 16.11.2	14.28	1929	192930133
2019 Update 9	Visual Studio 2019 version 16.9.2	14.28	1928	192829913
2019 Update 8	Visual Studio 2019 version 16.8.2	14.28	1928	192829334
2019 Update 8	Visual Studio 2019 version 16.8.1	14.28	1928	192829333
2019 Update 7	Visual Studio 2019 version 16.7	14.27	1927	192729112
2019 Update 6	Visual Studio 2019 version 16.6.2	14.26	1926	192628806
2019 Update 5	Visual Studio 2019 version 16.5.1	14.25	1925	192528611
2019 Update 4	Visual Studio 2019 version 16.4.0	14.24	1924	192428314
2019 Update 3	Visual Studio 2019 version 16.3.2	14.21	1923	192328105
2019 Update 2	Visual Studio 2019 version 16.2.3	14.21	1922	192227905
2019 Update 1	Visual Studio 2019 version 16.1.2	14.21	1921	192127702
2019	Visual Studio 2019 version 16.0.0	14.20	1920	192027508
2017 Update 9	Visual Studio 2017 version 15.9.11	14.16	1916	191627030
2017 Update 9	Visual Studio 2017 version 15.9.7	14.16	1916	191627027
2017 Update 9	Visual Studio 2017 version 15.9.5	14.16	1916	191627026
2017 Update 9	Visual Studio 2017 version 15.9.4	14.16	1916	191627025
2017 Update 9	Visual Studio 2017 version 15.9.1	14.16	1916	191627023
2017 Update 9	Visual Studio 2017 version 15.9.0	14.16	1916
2017 Update 8	Visual Studio 2017 version 15.8.0	14.15	1915
2017 Update 7	Visual Studio 2017 version 15.7.5	14.14	1914	191426433
2017 Update 7	Visual Studio 2017 version 15.7.3	14.14	1914	191426430
2017 Update 7	Visual Studio 2017 version 15.7.2	14.14	1914	191426429
2017 Update 7	Visual Studio 2017 version 15.7.1	14.14	1914	191426428
2017 Update 6	Visual Studio 2017 version 15.6.7	14.13	1913	191326132
2017 Update 6	Visual Studio 2017 version 15.6.6	14.13	1913	191326131
2017 Update 6	Visual Studio 2017 version 15.6.4	14.13	1913	191326129
2017 Update 6	Visual Studio 2017 version 15.6.3	14.13	1913	191326129
2017 Update 6	Visual Studio 2017 version 15.6.2	14.13	1913	191326128
2017 Update 6	Visual Studio 2017 version 15.6.1	14.13	1913	191326128
2017 Update 6	Visual Studio 2017 version 15.6.0	14.13	1913	191326128
2017 Update 5	Visual Studio 2017 version 15.5.7	14.12	1912	191225835
2017 Update 5	Visual Studio 2017 version 15.5.6	14.12	1912	191225835
2017 Update 5	Visual Studio 2017 version 15.5.4	14.12	1912	191225834
2017 Update 5	Visual Studio 2017 version 15.5.3	14.12	1912	191225834
2017 Update 5	Visual Studio 2017 version 15.5.2	14.12	1912	191225831
2017 Update 4	Visual Studio 2017 version 15.4.5	14.11	1911	191125547
2017 Update 4	Visual Studio 2017 version 15.4.4	14.11	1911	191125542
2017 Update 3	Visual Studio 2017 version 15.3.3	14.11	1911	191125507
2017 Update 2 ^†3	Visual Studio 2017 version 15.2	14.10	1910	191025017
2017 Update 1 ^†3	Visual Studio 2017 version 15.1	14.10	1910	191025017
2017	Visual Studio 2017 version 15.0	14.10 ^†4	1910	191025017
2015 Update 3	Visual Studio 2015 Update 3 [14.0]	14.0	1900	190024210
2015 Update 2	Visual Studio 2015 Update 2 [14.0]	14.0	1900	190023918
2015 Update 1	Visual Studio 2015 Update 1 [14.0]	14.0	1900	190023506
2015	Visual Studio 2015 [14.0]	14.0	1900	190023026
2013 Nobemver CTP	Visual Studio 2013 Nobemver CTP [12.0]	12.0	1800	180021114
2013 Update 5	Visual Studio 2013 Update 5 [12.0]	12.0	1800	180040629
2013 Update 4	Visual Studio 2013 Update 4 [12.0]	12.0	1800	180031101
2013 Update 3	Visual Studio 2013 Update 3 [12.0]	12.0	1800	180030723
2013 Update 2	Visual Studio 2013 Update 2 [12.0]	12.0	1800	180030501
2013 Update2 RC	Visual Studio 2013 Update2 RC [12.0]	12.0	1800	180030324
2013 Update 1 ^†3	Visual Studio 2013 Update 1 [12.0]	12.0	1800	180021005
2013	Visual Studio 2013 [12.0]	12.0	1800	180021005
2013 RC	Visual Studio 2013 RC [12.0]	12.0	1800	180020827
2013 Preview	Visual Studio 2013 Preview [12.0]	12.0	1800	180020617
2012 November CTP	Visual Studio 2012 November CTP [11.0]	11.0	1700	170051025
2012 Update 4	Visual Studio 2012 Update 4 [11.0]	11.0	1700	170061030
2012 Update 3	Visual Studio 2012 Update 3 [11.0]	11.0	1700	170060610
2012 Update 2	Visual Studio 2012 Update 2 [11.0]	11.0	1700	170060315
2012 Update 1	Visual Studio 2012 Update 1 [11.0]	11.0	1700	170051106
2012	Visual Studio 2012 [11.0]	11.0	1700	170050727
2010 SP1	Visual Studio 2010 SP1 [10.0] Visual C++ 2010 SP1 [10.0]	10.0	1600	160040219
2010	Visual Studio 2010 [10.0] Visual C++ 2010 [10.0]	10.0	1600	160030319
2010 Beta 2	Visual Studio 2010 Beta 2 [10.0]	10.0	1600	160021003
2010 Beta 1	Visual Studio 2010 Beta 1 [10.0]	10.0	1600	160020506
2008 SP1	Visual Studio 2008 SP1 [9.0] Visual C++ 2008 SP1 [9.0]	9.0	1500	150030729
2008	Visual Studio 2008 [9.0] Visual C++ 2008 [9.0]	9.0	1500	150021022
2008 Beta 2	Visual Studio 2008 Beta 2 [9.0]	9.0	1500	150020706
2005 SP1	Visual Studio 2005 SP1 [8.0] Visual C++ 2005 SP1 [8.0]	8.0	1400	140050727
2005	Visual Studio 2005 [8.0] Visual C++ 2005 [8.0]	8.0	1400	140050320
2005 Beta 2	Visual Studio 2005 Beta 2 [8.0]	8.0	1400	140050215
2005 Beta 1	Visual Studio 2005 Beta 1 [8.0]	8.0	1400	140040607
	Windows Server 2003 SP1 DDK (for AMD64)		1400	140040310
2003 SP1	Visual Studio .NET 2003 SP1 [7.1] Visual C++ .NET 2003 SP1 [7.1]	7.1	1310	13106030
	Windows Server 2003 SP1 DDK		1310	13104035
2003	Visual Studio .NET 2003 [7.1] Visual C++ .NET 2003 [7.1]	7.1	1310	13103077
	Visual Studio Toolkit 2003 [7.1]	7.1	1310	13103052
2003 Beta	Visual Studio .NET 2003 Beta [7.1]	7.1	1310	13102292
	Windows Server 2003 DDK		1310	13102179
2002	Visual Studio .NET 2002 [7.0] Visual C++ .NET 2002 [7.0]	7.0	1300	13009466
	Windows XP SP1 DDK		1300	13009176
6.0 SP6	Visual Studio 6.0 SP6 Visual C++ 6.0 SP6	6.0	1200	12008804
6.0 SP5	Visual Studio 6.0 SP5 Visual C++ 6.0 SP5	6.0	1200	12008804
	Visual Studio 97 [5.0] Visual C++ 5.0	5.0	1100
	Visual C++ 4.2	4.2	1020
	Visual C++ 4.1	4.1	1010
	Visual C++ 4.0	4.0	1000
	Visual C++ 2.0	2.0	900
	Visual C++ 1.0	1.0	800
	Microsoft C/C++ 7.0		700
	Microsoft C 6.0		600

Remarks

^ The product name column contains the Visual C ++ compiler and the actual product to be obtained It shows the name. Omit product edition (Express / Standard / Professional / Enterprise / Community etc.). The product version of Visual Studio is written in [~] when it does not appear in the product name. After 2017, We will adopt he product version that can be confirmed at [Help] - [version information of Microsoft Visual Studio] of the main menu.
^ In the VC ++ version column, describe the version of the Visual C ++ toolset. This table deals with only the tool set which is selected by default, especially when Visual C ++ is installed. In Visual Studio 2022, it can be found as folder name under C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC (such as 14.39.33519).
^ ^a ^b ^c Only IDE has been modified and compiler, The library etc was not changed.
- C++17 Features And STL Fixes In VS 2017 15.3 | Visual C++ Team Blog - "After VS 2017 RTM, the 15.1 and 15.2 updates improved the IDE. The 15.3 update improves both the IDE and the toolset."
- Description of Visual Studio 2013 Update 1
^ Since 2017 is binary compatible with 2015, 2017 is not a major upgrade. As a result, the product version and Visual C++ version has been no longer matched. Binary Compatibility and Pain-free Upgrade: Why Moving to Visual Studio 2017 is almost “too easy”

Since Visual Studio 2015, Visual C ++ is no longer in the default installation of Visual Studio. You need to select the Visual C ++ component in Visual Studio installer. See [Warning] in Visual C ++ for Visual Studio 2015.
2017 Update 5 now supports side-by-side, allowing you to select multiple Visual C ++ toolsets at the same time in one product. Side-by-side minor version MSVC toolsets in Visual Studio 2017 | Visual C++ Team Blog