4 ms·
The new terminal is pretty good, but what's more impressive to me about this is how bad it is. It's so clearly incomplete that opening the preferences launched
by pvh 7y ago
The new terminal is pretty good, but what's more impressive to me about this is how bad it is.
It's so clearly incomplete that opening the preferences launched a JSON editor window in Visual Studio (not VSCode).
The level of openness it takes to open such a central utility built by what would historically be a low-profile team is quite remarkable, and I am convinced will result in an excellent product ... in time.
For now? It's almost good enough to be my daily driver but not quite.
Good luck to the development team! I'll be watching.
- nevi-me 7y agoChange the default JSON editor from Visual Studio to VS Code, and you'll tick that checkbox. When I read the documentation before I installed it, there was a part that said that the JSON config file would open in the preferred JSON editor. It must be Visual Studio in your case.
- pography 7y agoMight be your system file settings. Mine opened up in VSCode, talking of which, don't forget that VSCode also opened a JSON file long before they added the settings interface. I couldn't find documentation for settings either so don't fully know what's capable but they do seem limited for now.
- bin0 7y agoCan confirm; it opens the default .json file editor. It's whatever the default setting is (which was VS2019 for me, as I don't work with json and didn't have it set).