How to modify or personalize the appearance of all your Microsoft Visual Studio windows, including Terminals, with your preferred font and color scheme.
Do you ever find yourself reminiscing about the good old days of Windows, or perhaps you've just got a natural inclination for personalizing everything you lay your hands on? Well, you're not alone. Many of us share that same itch for customization, especially when it comes to our development tools.
In this blog post, we'll dive into how you can infuse a dash of personality and style into Microsoft Visual Studio by harnessing the power of Nerd Fonts. But to get there, we'll need some essential tools and tricks in our toolbox.
The result of my customization looks like this:
Before we embark on this journey of customization, let's gather the essentials:
Now that we've got our toolkit ready, let's explore how we can make Visual Studio truly our own.
As you embark on this journey of customization, you'll likely encounter a minor hiccup—Visual Studio's Terminal Window. While we may have made peace with all the fancy clutter in the Windows Terminal, Visual Studio's Terminal doesn't always play nice with the custom fonts that OhMyPosh brings to the table. The result? A less-than-ideal appearance.
But don't worry; Visual Studio, a versatile tool that's been around since the '90s, offers a way out. You can customize the terminal font to align with your Nerd Font preference. Here's how:
2) The "Tools" > "Options" > "Fonts and Colors." Dialog
In this dialog, you have the power to customize the font and color settings for a wide range of elements within Visual Studio, including its various windows and docks. Importantly, among these elements, the Terminal is one that can be finely tailored to your preferences.
Finally this options allows you to use the same Nerd Font settings as your already customized Windows Terminal, achieving a unified and stylish appearance, like this:
Now, let's talk about the real beauty of this customization journey: flexibility.
As we grow older (and hopefully wiser), our eyesight might not be as sharp as it once was. But Visual Studio has got our back.
The ability to adopt different font sizes in various windows and docks within Visual Studio is a feature that's incredibly welcome. Whether it's increasing the font size for better readability or decreasing it to fit more information on the screen, you can fine-tune your coding environment to suit your needs.
Since Visual Studio gets a major UI/UX overhaul lets hope this feature will still remain.
In the end, Visual Studio, along with the power of Nerd Fonts, Windows Terminal WSL2, and OhMyPosh, offers a level of customization that lets you craft a development environment that truly feels like home. It's a blend of nostalgia, personalization, and functionality that helps you work comfortably and efficiently.
So, if you're like me—a '90s kid with a penchant for personalization—dive into Visual Studio's customization options and make it your own. Your coding journey may not be more productive but a touch more stylish and nostalgic.
Happy coding!
I think there might be a bit of a misunderstanding here - there are two different kinds of applications we're talking about here:
cmd.exe, powershell, zsh, etc. These are text-only applications that emit streams of characters. They don't care at all about how they're eventually rendered to the user. These are also sometimes referred to as "commandline client" applications.On Windows, if you just runcmd.exedirectly, the OS will create an instance ofconhost.exeas the terminal forcmd.exe. The same thing happens forpowershell.exe, the system will creates a new conhost window for any client that's not already connected to a terminal of some sort. This has lead to an enormous amount of confusion for people thinking that a conhost window is actually a "cmdwindow".cmdcan't have a window, it's just a commandline application. Its window is always some other terminal.
Any terminal can run any commandline client application. So you can use the Windows Terminal to run whatever shell you want. I use mine for both cmd and powershell, and also WSL:
It's not the Terminal's responsibility to remember the commands executed by a commandline client. That's the responsibility of the shell. How would the terminal remember commands executed by something likeemacsorvim? Those are both applications where the user is typing input and hitting enter, like they would at a cmd prompt, but without something that resembles a command history.
Original Source: #6500 (comment)
ryanoasisryanoasis
Edmund Leibert III