nvim 0.7.0 + windows terminal preview, [[0 escape sequence is inserted upon exit #17828

Closed
opened 2026-01-31 05:55:41 +00:00 by claunia · 3 comments
Owner

Originally created by @zeroxia on GitHub (Jun 30, 2022).

Windows Terminal version

Windows Terminal Preview
1.14.1451.0

Windows build number

10.0.19044.0

Other Software

neovim 0.7.0, 0.8.0

Steps to reproduce

Both the following neovim versions demo the same issue:

  • neovim 0.7.0 installed with scoop.
  • neovim 0.8.0 is portable version extracted to C:\usr\local

With Windows Terminal (preview), when exiting from nvim.exe, there is always a escape sequence [0 inserted at command prompt. There is no difference for cmd.exe, pwsh, powershell inside Windows Terminal.

If run nvim.exe in cmd.exe, there is no such issue. In cmd.exe, I can run pwsh or powershell, and then execute nvim.exe, still no issue after exiting.

animation showing the issue

Expected Behavior

No [0 sequence is inserted after exiting nvim.exe

Actual Behavior

[0 is inserted after exiting nvim.exe.

Originally created by @zeroxia on GitHub (Jun 30, 2022). ### Windows Terminal version Windows Terminal Preview 1.14.1451.0 ### Windows build number 10.0.19044.0 ### Other Software neovim 0.7.0, 0.8.0 ### Steps to reproduce Both the following neovim versions demo the same issue: * neovim 0.7.0 installed with scoop. * neovim 0.8.0 is portable version extracted to C:\usr\local With Windows Terminal (preview), when exiting from `nvim.exe`, there is always a escape sequence `[0` inserted at command prompt. There is no difference for `cmd.exe`, `pwsh`, `powershell` inside Windows Terminal. If run `nvim.exe` in `cmd.exe`, there is no such issue. In `cmd.exe`, I can run `pwsh` or `powershell`, and then execute `nvim.exe`, still no issue after exiting. ![animation showing the issue](https://i.imgur.com/DW0JG6X.gif) ### Expected Behavior No `[0` sequence is inserted after exiting `nvim.exe` ### Actual Behavior `[0` is inserted after exiting `nvim.exe`.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:55:41 +00:00
Author
Owner

@j4james commented on GitHub (Jun 30, 2022):

This looks like #13238. There's a fix committed already, but it just hasn't been released yet.

@j4james commented on GitHub (Jun 30, 2022): This looks like #13238. There's a fix committed already, but it just hasn't been released yet.
Author
Owner

@DHowett commented on GitHub (Jun 30, 2022):

Indeed! This is a /dupe of #13238.

@DHowett commented on GitHub (Jun 30, 2022): Indeed! This is a /dupe of #13238.
Author
Owner

@ghost commented on GitHub (Jun 30, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jun 30, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17828