| Actually, you're not stuck here, if you run into issues. You have both: --export --import options available to you for your WSL instances. You can get your configuration just so, then export it to a tarball that you can use for a baseline for later, that you can import it later. Or you can use Store apps to handle that operation for you. I'm thinking of the subscription-based app called "Raft WSL" that handles that for you. "…I wouldn't consider WSL stable." - It's not perfect, but it's sufficient to get me off of being a Mac user for 15+ years. Other than the polish of iTerm2, it gave me everything I had on Mac, without all the Mac-isms that I didn't like. Windows Terminal has proven to work very well for my dev-on-Windows needs. One of the BIGGEST factors in making this setup my choice is that Microsoft actually works on stuff, AND listens to their customers. Do you get everything you want? Certainly not. Do you get feedback when you report stuff? Very often, yes. Even if it's just to say "Yep, we know about this, we're working on it." Where, when you'd report a bug to Apple - you get nothing. Ever. Microsoft actually seems to CARE about making theirs the premier dev platform, where Apple only seems to care about new shiny, gives lip service to open source, and gives no responses to feedback. ¯\_(ツ)_/¯ |