You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Preview actions did not exit correctly. The occurrence of the problem may be related to the commit of 'Preview actions from the command palette on mouse hover' #18737
Éléa Dufresne (@eleadufresne) Could you please confirm if it is related to your commit.
The occurrence of the problem may be related to the commit of 'Preview actions from the command palette on mouse hover'. It looks like this, but I can't be entirely sure.
Éléa Dufresne (@eleadufresne) We used to have an issue like this with the keyboard previews for sendInput actions, but I think we fixed it at some point. Mouse previews may have reintroduced it? 🙂
When I switched the tag to '1.22.10731.0' in the code repository, I found that it didn't seem to contain this commit a86c90a. I apologize for the misunderstanding caused by this, Éléa Dufresne (@eleadufresne) . Perhaps this issue is not related to this commit a86c90a.
Now I have no idea what the cause of the problem is.
However, I also look forward to you @ eleadufresne taking a look at this issue when you have time. It may be a new opportunity to submit a pull request.
Finally, thank you for your contribution to Windows Terminal, as you and all the contributors have made it even better.
I'm using Windows Terminal Preview (v 1.24.2372.0) and I have a bunch of actions in my settings.json.
It seems for some input actions, if they appear first in the command palette list of commands, they cause the issue described.
For example I had an action like this which caused the issue:
Activity
DHowett commentedon Apr 2, 2025
Éléa Dufresne (@eleadufresne) We used to have an issue like this with the keyboard previews for
sendInputactions, but I think we fixed it at some point. Mouse previews may have reintroduced it? 🙂actanta commentedon Apr 3, 2025
When I switched the tag to '1.22.10731.0' in the code repository, I found that it didn't seem to contain this commit a86c90a. I apologize for the misunderstanding caused by this, Éléa Dufresne (@eleadufresne) . Perhaps this issue is not related to this commit a86c90a.
Now I have no idea what the cause of the problem is.
However, I also look forward to you @ eleadufresne taking a look at this issue when you have time. It may be a new opportunity to submit a pull request.
Finally, thank you for your contribution to Windows Terminal, as you and all the contributors have made it even better.
eleadufresne commentedon Apr 4, 2025
Thanks for the clarification, actanta. I’ll take a closer look when I have time!
Always glad to help 🙂
niall83 commentedon Sep 15, 2025
I'm using Windows Terminal Preview (v 1.24.2372.0) and I have a bunch of actions in my settings.json.
It seems for some input actions, if they appear first in the command palette list of commands, they cause the issue described.
For example I had an action like this which caused the issue:
{ "command": { "action": "sendInput", "input": "aws s3 ls s3://bucket/\r" }, "name": "abc" }Changing it to the following resolved the issue for me (by moving it to the end of the list of commands in the command palette):
{ "command": { "action": "sendInput", "input": "aws s3 ls s3://bucket/\r" }, "name": "Z abc" }actanta commentedon Sep 18, 2025
niall83 Thank you for providing the solution. My current solution is to add a command with no text preview as the top priority.
{ "command": { "action": "scrollDown", "input": "" }, "id": "User.sendInput.A061BCD", "name": "0.a" }Check for command palette's visibility before responding to search te…
Check for command palette's visibility before responding to search te…