Ueli does not work when VSCode is running about ueli HOT 7 CLOSED

Maybe a VS Code keyboard shortcut is interfering? Have you tried resetting VS Code settings completely?

from ueli.

@dasuppan I guess you have created a shortcut to launch the "code" CLI command right? That would explain the behavior, as the command line shortcut has a limitation as it waits for the program to exit. In your case, ueli waits until vscode exists. I suggest creating a shortcut that opens the executable file via file path instead.

Here is an example:

from ueli.

Unfortunately this has turned out to be intermittent. It will work fine for a while, and then suddenly Ueli won't work until I exit VSCode. I haven't figured out a reproducible trigger for it. I'll keep track of it and see if I can figure out what causes it to happen, but for now I don't think there is much you can do. Thanks,

from ueli.

I am having the same experience: Once I start vscode via the ueli bar (I have a shortcut "vscode" there) the bar does not take any keystrokes, the input field does not even show a cursor. After restarting ueli it works again. Sometimes when I then try to start vscode it will work just fine, even after vscode has opened. When I close vscode and run it once again the error occurs again. I am running on Windows 11.

from ueli.

Thanks! That resolved the issue. 👍

from ueli.

@dm413 I guess you have the same issue?

from ueli.

It's probably the same issue. A while back I switched to starting VSCode from xplorer2 (a windows file explorer replacement), and removed the shortcut in Ueli. This seemed to resolve the issue, though I didn't realize it was the Ueli shortcut itself that was the problem. I just now tested starting VSCode from Ueli using a file based shortcut rather than a command line one, and it works OK. Thanks,

from ueli.