95b3002201
The externalConsole=true setting is broken for many users (launching the debugger with such setting results in VS Code waiting forever without actually starting the debugger). Also, this setting is a matter of user preference, and is arguably better set in a "launch" section in the user-wide settings.json than hardcoded in our script. Remove the line to use VS Code's default, or the user's setting. Add useful links in contrib/vscode/README.md to help the user to configure VS Code and how to use the debugging feature. Helped-by: Matthieu Moy <Matthieu.Moy@univ-lyon1.fr> Helped-by: Derrick Stolee <derrickstolee@github.com> Co-authored-by: BRESSAT Jonathan <git.jonathan.bressat@gmail.com> Signed-off-by: COGONI Guillaume <cogoni.guillaume@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
19 lines
995 B
Markdown
19 lines
995 B
Markdown
Configuration for VS Code
|
|
=========================
|
|
|
|
[VS Code](https://code.visualstudio.com/) is a lightweight but powerful source
|
|
code editor which runs on your desktop and is available for
|
|
[Windows](https://code.visualstudio.com/docs/setup/windows),
|
|
[macOS](https://code.visualstudio.com/docs/setup/mac) and
|
|
[Linux](https://code.visualstudio.com/docs/setup/linux). Among other languages,
|
|
it has [support for C/C++ via an extension](https://github.com/Microsoft/vscode-cpptools) with
|
|
[debugging support](https://code.visualstudio.com/docs/editor/debugging)
|
|
|
|
To get help about "how to personalize your settings" read:
|
|
[How to set up your settings](https://code.visualstudio.com/docs/getstarted/settings)
|
|
|
|
To start developing Git with VS Code, simply run the Unix shell script called
|
|
`init.sh` in this directory, which creates the configuration files in
|
|
`.vscode/` that VS Code consumes. `init.sh` needs access to `make` and `gcc`,
|
|
so run the script in a Git SDK shell if you are using Windows.
|