1. 22
  1.  

  2. 14

    The instructions in this post are great, and if you live and breathe *nix, it’s indeed a great way to bring all your existing tools over. That said, if you’re doing this purely because you’re disappointed with the speed/quality of the Windows console, I’d really encourage you to follow along with the Windows Terminal betas instead. You’ll get tabs, proper colors, drastically improved speed, etc. but you can use the same terminal for both the Windows and Linux side, plus you don’t need to install and configure X, and you’ll get better integration with the rest of the host OS.

    The other thing I’d personally probably do before this is use Hyper.js (which ≥v3.0 is actually very fast), but I totally grok why going that route might feel a bit too gross.

    1. 3

      Slightly sheepishly also using Windows after it came on my new laptop and I wanted to see what power and screen management was like before I nuked it.

      @gecko @timvisee What do you think of the new Windows Terminal so far? I’ve found it ok - annoyingly there are a couple of tmux/vim keys that it caught but otherwise seems nice so far.

      1. 7

        It’s moving fast, so it’s hard for me to really have a strong opinion on it at the moment. The initial launch was crashy and had issues with 256 color support. It’s now relatively stable (in a crashing sense), and colors are better, but there’s still just tons of little things that aren’t 100% there yet. Scrolling is smooth except when it isn’t, there are some odd keybinding collisions that I’m not sure are from WSL or from Terminal or what, and so on. I chose my word choice of “…follow along with” instead of “use” on purpose; I’m really excited and pretty confident about where it’s going, but I’m not convinced it’s there yet for everyone, either.

        1. 3

          I’ve only used it for a short while, and that was some time ago. For what I recall, I had trouble with rendering xterm-256colors, and some bindings I used where caught (like you’re experiencing). I should give it another try with a fresh build, it might be better now, so don’t quote me on it. It’s in rapid development after all.

          Based on that experience I do agree that it is ok, but not good enough. It doesn’t work as well (yet) as the solution I’ve suggested with the XFCE terminal, even though that takes some effort to set up. There are some minor annoyances with broke the awesome terminal feeling for me, and I’m done tinkering around with all kinds of settings.

        2. 2

          Thanks. I totally agree that this is intended for *nix power users, and might edit the post to make that a bit more clear.

          I really hope the Windows Terminal will get as plug and play as current terminals on Linux when it is released, that would be awesome.

          1. 3

            It should. Windows Terminal will be replacing the existing Windows console client once it’s finished, and Windows console is already the default terminal used for both WSL 1 and 2, so the overall effect should be that you get a native, actually good terminal with your pseudonative Linux installation out-of-the-box. (If you opt in the Insider previews, you can live in this world now.) Things can always change before shipping, but right now, it looks very promising.

          2. 2

            Don’t forget the smileys! (Or whatever they are called these days)

          3. 4

            I’ve been doing this for a while and it works ok, copy paste takes a few attempts sometimes and generally it’s not as good as it should be. But then all the native windows terminals are just awful (how does opening a box with text take multiple seconds????) and this works a lot better.

            For actually starting terminals I have this autohotkey script:

            #Enter::
            	Run C:\Program Files\Alpine Linux\st.vbs
            	WinWait Xming,, 1
            	if ErrorLevel = 0
            		WinMaximize
            	return
            

            and st.vbs is:

            WScript.CreateObject( "shell.application" ).ShellExecute "C:\Program Files\Alpine Linux\Alpine.exe", "run cd;env DISPLAY=:0 st", "", "open", 0
            
            1. 3

              Never thought about autohotkey/VBS, those snippets are actually quite useful, thanks for sharing!

              I have not had any issues with the clipboard myself (other than regular command-line clipboard issues also present on Linux and macOS), and syncing it between X and a X server on Windows seems to work fine.

            2. 3

              No mention of Cygwin?

              https://cygwin.com

              1. 3

                I can’t cover every tool in a post, but I did give it a try. Cygwin is an awesome project, but I didn’t succeed in properly rendering the tool I’m using, and it isn’t a WSL replacement for me because:

                Cygwin is not: a way to run native Linux apps on Windows. You must rebuild your application from source if you want it to run on Windows.

                1. 5

                  I try really hard to make blanket statements like this, but:

                  in the world of WSL, I can think of absolutely zero reasons to use Cygwin, and a lot of reasons not to. So I don’t think you’re missing anything.

                  1. 2

                    Agreed. This was a valliant effort and did a Yoeman’s job for many a year, but its time has past.

                2. 3

                  Cygwin is a worse distro than any normal linux and way way slower than WSL

                  1. 2

                    way way slower than WSL

                    I am not saying youre wrong, but do you have any data to back this up?

                    I am pretty skeptical of this statement. Also some other issues:

                    1. 2

                      No I never measured, but I remember it being immediately apparent that WSL was faster when I switched over

                3. 2

                  ConEmu https://conemu.github.io is , by far, the best Windows terminal emulator. Just use that.

                  1. 3

                    It doesn’t work, at all, for what I’m trying to do.
                    It looks similar to CMDer, which is in the top left of this screenshot: https://timvisee.com/blog/fix-windows-terminals-use-linux-terminal/overview.png

                  2. 2

                    Thanks for this. I may give Windows Terminal a try but if that’s not prime time enough for me yet I may go this route.

                    I tried this before using the [Commercial build of XMing but could never get any sane fonts to render correctly so I gave up, admittedly without engaging the offered support.