I wish my code was half as good as my expectations for how my code should be. My lattes are better than my code, so maybe I should make latte art instead of ascii art
An interesting setup I've been looking into trying recently was something I've seen Scott Hanselman champion:
Using the Windows Terminal with WSL2 (so you get an actual linux shell from inside the ubuntu distro), and connecting VS Code to the same WSL2 instance, so the terminal in VS Code is also the terminal in the WSL.
It might seem like a really contrived example, and completely over the top depending on your needs, but worth checking out if you start getting into the windows/*nix compatibility issues, if you're doing some cross platform development, or if you are trying to program in a language that has better support in Linux-land.
Welcome tag moderator AKA Unofficial DEV cheerleader. While most of my friends are found on SnapChat or Tic-Toc, you can find me here. And I OOP, but I’m not a VSCO girl.
Okay. So for that it looks like I have to install WSL, and Ubuntu, and then install WSL2, and then run out of VS Code.
Seems like a lot of work that's going to take some time.
Something to think about when I have some idle time (which are few and far between these days).
I wish my code was half as good as my expectations for how my code should be. My lattes are better than my code, so maybe I should make latte art instead of ascii art
Yup, that is pretty much the gist of it. Unfortunately this isn't a trivial setup, as you've said.
I used Cmder a lot coupled with the git bash shell for windows, and that setup was pretty solid too.
The cool thing about this is that any one developer's terminal and console setup will be completely different from one to another. My current setup on a mac is using zsh for the terminal shell, iterm2 for terminal, and I use applescript to actually configure pane splitting in iterm2, because I'm basically replicating what I used to have with Cmder when I was on windows.
It would be really interesting if you wrote another post a few months from now to describe all the combinations you tried and which ones you decided to stick with, and why. It's always nice to see what other people are doing. @aspittel
had a really cool post where the community was sharing their own setup. Might be a cool place to get some more ideas as well: dev.to/aspittel/what-does-your-ter...
Welcome tag moderator AKA Unofficial DEV cheerleader. While most of my friends are found on SnapChat or Tic-Toc, you can find me here. And I OOP, but I’m not a VSCO girl.
I'll take a look at that post and make a mental note to do a follow up.
Another addition will be that PowerShell 7 is due to release soon. For those of us on Windows, that will be something else to learn if you do a lot of scripting in that environment.
Now that I think about it, if I wait too long to do the follow up, the whole console world could change!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
An interesting setup I've been looking into trying recently was something I've seen Scott Hanselman champion:
Using the Windows Terminal with WSL2 (so you get an actual linux shell from inside the ubuntu distro), and connecting VS Code to the same WSL2 instance, so the terminal in VS Code is also the terminal in the WSL.
It might seem like a really contrived example, and completely over the top depending on your needs, but worth checking out if you start getting into the windows/*nix compatibility issues, if you're doing some cross platform development, or if you are trying to program in a language that has better support in Linux-land.
Here's the link to the video if this setup piqued your interest:
youtube.com/watch?v=A0eqZujVfYU
Okay. So for that it looks like I have to install WSL, and Ubuntu, and then install WSL2, and then run out of VS Code.
Seems like a lot of work that's going to take some time.
Something to think about when I have some idle time (which are few and far between these days).
Thanks for the reply Aimeri and the video link.
Yup, that is pretty much the gist of it. Unfortunately this isn't a trivial setup, as you've said.
I used Cmder a lot coupled with the git bash shell for windows, and that setup was pretty solid too.
The cool thing about this is that any one developer's terminal and console setup will be completely different from one to another. My current setup on a mac is using zsh for the terminal shell, iterm2 for terminal, and I use applescript to actually configure pane splitting in iterm2, because I'm basically replicating what I used to have with Cmder when I was on windows.
It would be really interesting if you wrote another post a few months from now to describe all the combinations you tried and which ones you decided to stick with, and why. It's always nice to see what other people are doing. @aspittel had a really cool post where the community was sharing their own setup. Might be a cool place to get some more ideas as well:
dev.to/aspittel/what-does-your-ter...
I'll take a look at that post and make a mental note to do a follow up.
Another addition will be that PowerShell 7 is due to release soon. For those of us on Windows, that will be something else to learn if you do a lot of scripting in that environment.
Now that I think about it, if I wait too long to do the follow up, the whole console world could change!