After struggling with sometimes not being able to type anything in UELI, I've narrowed the problem to the new Windows Terminal.
windows terminal (Preview) from UELI from a shortcut (type: "Commandline Tool", command: "wt")windows terminal (Preview) window that you openedWith a terminal window open, restarting UELI also fixes the problem, allowing you to use UELI freely.
Launching windows windows terminal (Preview) through another mechanism (without using UELI, or using ueli but choosing the UWP app instead of the shortcut) does not trigger the bug, and UELI remains usable.
I believe this is due to some weird interaction where launching a terminal window does not return control or does not inform UELI that the launch was successful. However, launching wt from cmd does not result in this bug, and cmd remains usable.
This is similar to #395 ,
Workflow too has the same issue, any plugin with commandlineExecutor funciton.
I will add a PR to fix this.
It does indeed seem to be the same issue (or at least very closely related).
By the way, this issue is still present in ueli 8.7.1, even though it was marked as fixed in #395
Yeah , the fix was for commandline plugin only, the issue in your case is with the shortcut plugin. The error is the same but in different plugins. I add a new PR to fix the error in both shortuctus and workflow plugins.
Once oliver approves and merges the PR, it will be fixed. So I hope it will be in the next release.
Most helpful comment
Yeah , the fix was for commandline plugin only, the issue in your case is with the shortcut plugin. The error is the same but in different plugins. I add a new PR to fix the error in both shortuctus and workflow plugins.
Once oliver approves and merges the PR, it will be fixed. So I hope it will be in the next release.