| commit | 0f47f78e02d16e6edd0448285815ccc1744294e8 | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Mon, 30 Jul 2018 15:42:52 +0000 (30 08:42 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 30 Jul 2018 20:14:39 +0000 (30 13:14 -0700) | ||
| tree | d9c1b5dba4114de511e8dd17ea8557efb97aad8d | treesnapshot (tar.gz zip) |
| parent | b4d991d1a2e2f5da6d3f08d82d1fa9ef45605e07 | commitdiff |
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>
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>
| contrib/vscode/init.sh | diffblobblamehistory |