git/contrib/vscode
Johannes Schindelin 0f47f78e02 vscode: only overwrite C/C++ settings
The C/C++ settings are special, as they are the only generated VS Code
configurations that *will* change over the course of Git's development,
e.g. when a new constant is defined.

Therefore, let's only update the C/C++ settings, also to prevent user
modifications from being overwritten.

Ideally, we would keep user modifications in the C/C++ settings, but
that would require parsing JSON, a task for which a Unix shell script is
distinctly unsuited. So we write out .new files instead, and warn the
user if they may want to reconcile their changes.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-07-30 13:14:39 -07:00
..
.gitattributes contrib: add a script to initialize VS Code configuration 2018-07-30 13:14:38 -07:00
init.sh vscode: only overwrite C/C++ settings 2018-07-30 13:14:39 -07:00
README.md contrib: add a script to initialize VS Code configuration 2018-07-30 13:14:38 -07:00

Configuration for VS Code

VS Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. Among other languages, it has support for C/C++ via an extension.

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.