I haven't benchmarked, but running WSL 2 feels so much snappier and I don't feel a noticable delay when running a large npm install. This comparsion on the MS site shows all the differences, but the highlight for me was that file IO performance was drastically improved - the docs quote 2-5x faster for running tools such as git or npm. I can't go into the details of the implementation, because frankly it's way over my head, but from the learnings of the successes and failures of WSl 1 Microsoft were able to make amazing improvements in WSL 2. WSL 2 (see an intro video here) promised major improvements over WSL 1. Not much, and not often, but everything wasn't quite as smooth as it would be on the MacBook I usually worked on. WSL 1 also had some holes in terms of application support, you couldn't use Docker - not something I do regularly, but something that's useful to be able to reach for - and at times I found the VSCode WSL integration to be slightly laggy. You might think this isn't a huge deal - but if you're running a package manager like npm and installing a bunch of dependencies, those reads and writes add up to the point where it's noticably slow (and I'm running on a fairly beefy XPS laptop). The main one was that WSL 1 was known to be much slower at file reads and writes. That said, there were some minor issues and frustrations with WSL and this workflow.
#Alacritty wsl2 windows
By using the Windows Subsystem for Linux (WSL), I was able to run most of my tools effectively in Linux, something I'm familiar with, and with VSCode's WSL Remote plugin, I could run VSCode in Windows connected to the Linux environment provided by WSL, and things felt very familiar.
#Alacritty wsl2 windows 10
I'd like to share with people the solution to solve this problem if anyone wonders how.DecemSoftware Development on Windows 10 with WSL2īack in October 2019 I'd taken the plunge and tried Windows for my development work. I think I can't delete it so I close the issue. I realized I might put the issue in the wrong place after keep trying to fix the bug. Neither "%V\\" nor "%V\" can solve the conflict two directories situation problem I indicated above. However, it fails when right-clicking on the background of the root directory (C, D, E, F, etc.) in file explorer. It looks like "%V\" only works fine when you right click directly on the drive (C, D, E, F, etc.)Īnd "%V\\" works fine when you right-click directly on directories (C:\Program Files, C:\ProgramFiles) or right-click on the background of directories (C:\Program Files, C:\ProgramFiles). Root: HKA Subkey: "Software\Classes\Drive\shell\Open WezTerm here" ValueName: "icon" ValueType: string ValueData: """ start -no-auto-connect -cwd ""%V\\""" Flags: uninsdeletekey Root: HKA Subkey: "Software\Classes\Drive\shell\Open WezTerm here" Flags: uninsdeletekey Here's my edited fork for the gist above in case someone needs it:
#Alacritty wsl2 code
I guess it might because of some of those variables that pass to them, and they considered this situation in the source code for reading directory string. I don't know why.Ĭmd and Powershell don't have this problem, they are fine with cmd.exe /s /k pushd "%V" and powershell.exe -noexit -command Set-Location -literalPath '%V' registry key value. Then I try "%V and it magically solves the problem. Then I try "%V\\" which is what the WezTerm terminal emulator did but also can't open at D:\ with right-click at the background.
Then I try "%V\", the same problem as above and even worse, you can't even open at D:\ProgramFiles which is a directory that doesn't contain space. I think it is because you need "" around D:\Program Files to compromise the space between Program Files. However, D:\Program Files is a problem and Alacritty will not open here. I guess it is because the backslash \ make " an escape character. However, D:\ directory will cause Alacritty to throw an error of Invalid working directory: "D:\"".
If I use "%V", right-click at the background open Alacritty here at D:\Program Files and D:\nospace will have no problem. However, I face two directory situations now that conflicts with each other.
I don't understand why there's an extra % after %V. When this added to the registry, the last variable of the key-value is "%V%".
Alacritty \"-working-directory\" \"%V%\""
0 kommentar(er)
