[O erroneously inputted after exiting from Neovim 0.7.0 in latest Terminal Preview #17650

Open
opened 2026-01-31 05:48:54 +00:00 by claunia · 0 comments
Owner

Originally created by @MatejKafka on GitHub (Jun 6, 2022).

Originally assigned to: @zadjii-msft on GitHub.

Windows Terminal version

1.14.1451.0

Windows build number

10.0.19044.1706

Other Software

Neovim 0.7.0 (https://github.com/neovim/neovim/releases/tag/v0.7.0)

Steps to reproduce

  1. Install Neovim
  2. Open it by running nvim in your shell (works both in cmd and pwsh)
  3. exit it (:q)

Expected Behavior

Neovim exits, nothing else happens.

Actual Behavior

Neovim exits, and the shell receives [O on its console input.

image

My guess would be that the characters are part of a response to some VT escape code from Neovim, but for some reason they get written separately and the shell gets them instead of Neovim.

Originally created by @MatejKafka on GitHub (Jun 6, 2022). Originally assigned to: @zadjii-msft on GitHub. ### Windows Terminal version 1.14.1451.0 ### Windows build number 10.0.19044.1706 ### Other Software Neovim 0.7.0 (https://github.com/neovim/neovim/releases/tag/v0.7.0) ### Steps to reproduce 1. Install Neovim 2. Open it by running `nvim` in your shell (works both in `cmd` and `pwsh`) 3. exit it (`:q`) ### Expected Behavior Neovim exits, nothing else happens. ### Actual Behavior Neovim exits, and the shell receives `[O` on its console input. ![image](https://user-images.githubusercontent.com/6414091/172247280-950814dc-16d4-4ff2-b46b-2dce47365c62.png) My guess would be that the characters are part of a response to some VT escape code from Neovim, but for some reason they get written separately and the shell gets them instead of Neovim.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17650