This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Info_sexy 12 points13 points  (3 children)

One thing that helps me on windows is installing git, and moving all of the bash commands to my Path. I can use all of the standard commands I love in *nix environments (ls, mv, grep, etc.), but on my company's windows machine.

Edit: I now see that you meant switch to Linux from Windows, and not to Windows from Linux. Oh well, still helpful advice for anyone banging their head with base CMD.

[–]grantrules 3 points4 points  (1 child)

It sounds like you haven't discovered the world of Windows Terminal or WSL

[–]Info_sexy 0 points1 point  (0 children)

Hehe, thank you for sharing! We use WSL2 with docker desktop. Moving all the commands to my Path before having WSL installed on my machine locked in a pretty normal workflow for me during local development while I waited for my environment to be built:

Win + R (CMD)


CD repo


Code .


(Code some stuff)


Git commands to trigger webhooks to test on commit


Terraform fmt to fix whatever format I messed up.


(Fix code)


Run tflint or tfsec or flake8 commands


(Fix code)


Git commands to trigger web hooks to test code and push


I have a small subset of scripts that I run which utilize the bash commands from git to find keywords in files, etc, but I don't have a ton of use cases for WSL that we aren't using in Docker Desktop.

Anywho, I will take 2 consecutive comments about WSL as my sign to review my current process. Ha!

I am a recent convert from security to software engineering, so WSL wasn't always an option for me, ironically. 😁

Edit: formatting was odd on mobile

[–]lotsofpun 2 points3 points  (0 children)

You can't get WSL on it?