Fork me on GitHub
#off-topic
<
2020-07-05
>
chucklehead00:07:52

As long as you keep your work within the WSL filesystem and stay away from accessing the Windows side via /mnt/c and the like the I/O performance should be relatively close to the host I/O perf. You can add exclusions in Defender on the Windows side to exclude scanning within the Windows-visible projection of the WSL filesystem to keep your project folders out of real-time scanning. It would be nice if this were easier. The editor experience with VSCode and the WSL remoting feature is pretty seamless. I’ve also tried Cider via Windows Terminal as well as using X410 with no issues. For what it’s worth I’m completely new to Clojure so I couldn’t say if it sucks compared to the native experience elsewhere, but no real issues yet for me using Ubuntu 20.04

sveri06:07:51

I have been co developing on windows / WSL with clojure for some time now. Which means I use Cursive in windows for editing and running my server / repl and the other clojure stuff (running tests / deps) I often do in WSL for the same project. Cannot say I noticed that any of that is particularly slow, but I also have m.2 ssd and assume that's mainly the reason for it.

borkdude09:07:27

Any advice on running Emacs in the new WSL2 Windows world?

chucklehead15:07:52

any particular problems you're running into? Using WSL2/Ubuntu 20.04 I just installed emacs directly from apt. I use https://x410.dev/ for the windows X client, which is a paid app, but should also work with Xming or VcXsrv. The only WSL2-specific thing I had to do was add this to .bashrc to extract the host's IP from resolv.conf and set the DISPLAY variable on login: [ -z $DISPLAY ] && export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}'):0.0 . I've also tried using it via emacs -nw with the new windows Terminal app. I did have some issues there with Terminal not being able to pass-through some modifier keys/key combinations correctly which is supposed to be fixed/improved in the most recent Terminal release but I haven't revisited.

borkdude18:07:07

@U015879P2F8 I haven't tried it yet, just gathering the best information I can get 🙂 For now I'm only interested in the GUI bit. X410 looks interesting, thanks for sharing

seancorfield18:07:26

I didn't even know there was a workable X option for WSL. Cool.

seancorfield18:07:33

Currently available for just $10 instead of the normal $50! (X410).

seancorfield18:07:16

Probably because MS have announced that they plan to make it possible to run GUI-based Linux apps natively on WSL2 "soon".

borkdude18:07:30

Interesting. Going to try it out now in Parallels (unfortunately I can't run WSL2 in my edition of Parallels though)

borkdude18:07:19

but WSL1 works, so I'll see if that works

seancorfield18:07:49

Same here. I have an ancient Windows laptop running Windows Home that doesn't seem capable of virtualization so I'm stuck with WSL1 there, and I use Parallels on macOS on my main machine so it's WSL1 there for the same reason.

borkdude18:07:13

Windows Home can run WSL2 since Windows 10 2004 released in May

borkdude18:07:34

Parallels Pro edition can do it, but I have the Home edition

seancorfield18:07:41

Ah, I remember someone mentioning that. I should try to upgrade my laptop... although rebuilding my WSL env there would be a pain.

borkdude19:07:08

Running my same Emacs config from macOS in WSL1 on Windows: https://twitter.com/borkdude/status/1279854040034226180

borkdude21:07:44

Has anyone by any chance have a setxkbmap config that works with an Apple magic keyboard with Dutch layout?

p-himik06:07:26

Don't know about the Dutch layout, but in order to make some keys like Eject and F13-F19 do something else, I had to patch the custom kernel module: https://github.com/free5lot/hid-apple-patched