<ul dir="auto">
<li>VSCode Version: 1.2.0</li>
<li>OS Version: Win 10 enterprise preview</li>
</ul>
<p dir="auto">Steps to Reproduce:</p>
<ol dir="auto">
<li>Set user setting to  "terminal.integrated.shell.windows": "%programfiles%\Git\git-bash.exe"</li>
<li>Open terminal ctrl+`</li>
</ol>
<p dir="auto">Expected:<br>
Terminal opens.</p>
<p dir="auto">Actual:<br>
Terminal window flickers and closes (presumably crashes).</p>
<p dir="auto">Workaround:<br>
Use explicit pathing like "C:\Program Files\Git\git-bash.exe" instead.</p>
<p dir="auto">I have a suite of projects that I'd like to have a shared configuration (e.g. all the repos at my company).</p>
<p dir="auto">Currently we have duplicate <code class="notranslate">.vscode/settings.json</code> files, and several common <code class="notranslate">.vscode/tasks.json</code> tasks. Some projects have additional tasks defined beyond the common ones.</p>
<hr>
<p dir="auto">I'm unsure what the right approach to take here is. I'd love some input</p>
<ul dir="auto">
<li>Can extensions apply user settings, or define tasks/problem matchers? The docs <a href="https://code.visualstudio.com/docs/extensionAPI/extension-points" rel="nofollow">don't seem to indicate that</a>.</li>
<li>Can a project declare a VS Code extension as a dependency? (seems unlikely, but hey :P)</li>
<li>We're toying with the idea of a common package with a <code class="notranslate">postinstall</code> script that symlinks the configuration in (and just over-defining tasks) - but it's pretty ugly.</li>
</ul>