It's probably the easiest to configure terminal ever...
https://www.hanselman.com/blog/HowToMakeAPrettyPromptInWindo...
> and opening Settings fires up Visual Studio of all things
Settings opens what ever editor is your default for .json files.
> with GUIDs that I have no idea what to do with
1 guid to identify each option?
I guess Windows Terminal was designed for developers and not users.
- Settings become more portable.
- Settings become more shareable.
That said, VS Code started with JSONC-based configs and now presents a UI by default (still editable directly as JSONC for those who prefer). It seems possible JSONC could be used to bootstrap a UI for Windows Terminal too if there's demand.
> Settings opens what ever editor is your default for .json files.
And one can also point out that macOS opens XCode for (even XML-based) .plist files.
It's getting to be a standard convention, now that IDEs are almost "ships with the OS" kind of software, that the OS thinks configuration files should be opened in the IDE, rather than the system GUI text editor (Notepad; TextEdit.) Because, I guess, the system text editors were never really made to edit code, and make no guarantee that they won't break the formatting of code, while IDEs do make that guarantee.
OS ranking is pretty much: MacOS > Windows > *nix garbage
Just missing a Quake mode for me (summon from a screen edge with a keyboard shortcut), but that's being talked about for v2. https://github.com/microsoft/terminal/issues/653
(For about 10 years, I've been using a bog-standard, symmetrical, 2-button scroll-wheel mouse by Logitech, and am looking to transition to a finger-operated trackball to save desk space, and just to see what the fuss is about.)
Very powerful.
But for now my 2017 macbook works well enough. I do think it's overpaid though; outside of the occasional nyan cat gimmick, I've NEVER used the touch pad. At the moment it's closed and to the side while I work on my external screens and the pretty decent Apple keyboard + mouse.