![]() I had to use a pretty hacky method involving accessing a hidden shell view in File Explorer to do so. Windows makes it very hard to make shortcuts to programs installed from the Microsoft Store. It seems like there should be a more straightforward way to do this.ītw, even just making that. Maybe there's a better way of making the keyboard shortcut than what I've used? It did seem weird to me that I had to make a file system shortcut (.lnk file) and then right click on it to register a keyboard shortcut. So this seems to have something to do with the shortcut mechanism. If I run windows terminal from the start menu it starts after what's maybe a 0.3 s delay. I just discovered that the slowdown only seems to occur when running it via the keyboard shortcut. Thanks to u/itsnotlupus for identifying the problem and giving a working solution! Much easier than the built-in way, and improtantly does not have the delay. I installed Clavier+, and it worked exactly how I thought keyboard shortcuts would work in the first place. ![]() A simple fix is to not let windows do that "ask everybody if they want to handle the shortcut thing" by using a 3rd party shortcut handler. So apparently there's often some program on my system that's unresponsive (apparently the windows settings app is sometimes the culprit). And more confusingly, sometimes (10-20% of the time maybe) the process is much faster, taking maybe 0.5 seconds.ĭo any of you know what could be causing this variable startup delay? And is there a better way of opening up a new terminal that doesn't have this problem? (Note: I don't just want a new tab in the same window - that already works fine)Įdit: The issue seems to be how windows asks every running program if it wants to handle a keyboard shortcut, with a timeout of 3 seconds for unresponsive programs. It's not clear to me why this happens, as each terminal still seems to be part of the same virtual machine, so no new virtual machine should be being started up, which I could see being slow. This setup works ok, but it has the annoying property that opening a new terminal window usually takes 3-5 seconds. With my workflow I often need to open up new terminals, so I've set the shortcut CTRL-F1 to open Windows Terminal with the WSL2 guest in it by setting arch as the default profile in Windows Terminal and registering CTRL-F1 as the keyboard shortcut in the properties menu of a Windows Terminal shortcut file. I'm using WSL2 version 1.0.3.0 (WSLg 1.0.47) on Windows 11 (1.963) with an Arch Linux guest.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |