https://github.com/microsoft/terminal
You still have to build it from source in VS 2017 or 2019, and there are a few rough edges (currently only middle click for copy/paste), but it's a great start. They should have some official binaries up pretty soon.
https://dev.azure.com/ms/Terminal/_build/results?buildId=203...
This way you are registering the app directly instead of installing the appx.
https://www.microsoft.com/en-us/p/windows-terminal-preview/9...
I've hence been avoiding volumes for things other than static files or backup/restore directories.
> Also, bind mounts from [Docker on WSL2] will support inotify events and have nearly identical I/O performance as on a native Linux machine, which will solve one of the major Docker Desktop pain points with I/O-heavy toolchains.
[0] https://magit.vc/manual/magit/Microsoft-Windows-Performance....
Although I admit, sometimes the BSD toolchain poses some rather hilarious speedbumps. At that point WSL can be smoother? Weird.
Can you go into more detail about why that's the case — package selection, versioning policies, etc.? The main thing I've typically found is testing version-matched deployments and Docker has made me care about that a lot less.
If the IT department prepared a pre setup image, all you need to do is boot it up.
https://github.com/mintty/wsltty
I've found it to be the most consistent and performant. Still not the same as being in a native Linux environment, of course, but it's the closest I've been able to get in Windows.
Also, copy/paste works perfectly and I found that fewer of the default keybindings conflict with those in my shell, tmux and vim.
I use wsltty for the terminal, it's pretty minimal, but better than the windows terminal.
It has 4 different paste methods in the settings, I encountered the bug on all at work. I've used it without encountering the bug before though, but I haven't figured out what causes it.
Second, why use a cross platform app inside VM? Using the VM only for command line interface through SSH will get rid of any lag. You can share the host OS file system inside the VM and use GUI app on the host OS against native file system and you won't have to worry about filling up VM disk.
Connecting some $1k MacBook Air to an external monitor + keyboard would get you a decent desktop experience which you can even take it out. Not sure how that is any expensive.
[0] https://code.visualstudio.com/docs/remote/remote-overview
Starting a new terminal with wsl1 takes so long and I'm less than happy with all terminal emulators.
ConEmu has broken copy paste, alacrity doesn't have proper tiling... Heck, I've started using hyper of all things.
I realize that I probably never be happy on Windows when I can actually use i3wm at home, but if it could just suck less I'd be so ecstatic.