Heath Stewart

For that matter, just checking `TERM` is not sufficient on any platform. See helper functions used by the cli/go-ch link above: .

Contains fix for #883 to unblock testing. Tested in Windows Terminal with bash (WSL) and pwsh.exe (WT uses conpty) and cmd.exe (which uses conhost).

I appreciate the original reason it was removed as well, but a dedicated search button for a feature I almost never use (since searching on Mastodon is quite limited by...

This is merely a lookup for previous versions, and both old and new versions of _VSIXInstaller.exe_ support `/q` for quiet installs. Filtering - and generall understanding - which command line...

> However, a solely \q is too likely to fail on VS15 without forcing the blocking processes to shutdown. If you are seeing UI pop up when there are processes...

After further discussion, we agree this is outside the original scope and not an investment we want to make at this time; however, if someone were to contribute back such...

Will do. With previous releases there was no cheap way to detect extensions' presence but the new query API could make that possible now for v3s (doesn't have to load...

Actually, that still wouldn't work for previous extension versions or on previous releases. If the DetectCondition were always false, it would at least attempt to install the extension each time...

This came up today in a discussion. Basically, there's no conceivable way to author a `DetectCondition` that works for multiple instances. This is why in [the WIP](http://wixtoolset.org/development/wips/5433-add-support-to-detect-and-install-vsix-packages-into-vs15/) I recommend generating...

The VSIXBootstrapper is just a thin wrapper around VSIXInstaller. If VSIXInstaller failed, as you noted above, please file a bug report at https://developercommunity.visualstudio.com.