[Bug] Weird Neovim output
Open
Nobody has claimed this yet.
🐛 Type: Bug
🤝 Help wanted
- Dominant language
- PowerShell
- Stars
- 27k
- Forks
- 2.1k
- PR merge metrics
- No merged PRs in 30d
Description
Version Information
Cmder version: 1.3.20.151
Operating system: Windows 10
Cmder Edition
Cmder Full (with Git)
Description of the issue
So, I'm a Windows Terminal who migrated to Cmder for some reasons. When I try opening Neovim, the output is just weird.
How to reproduce
- Open WSL: Debian.
- Typing
nvim. - Weird output.
Additional context
Checklist
- I have read the documentation.
- I have searched for similar issues and found none that describe my issue.
- I have reproduced the issue on the latest version of Cmder.
- I am certain my issues are not related to ConEmu, Clink, or other third-party tools that Cmder uses.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Reproduce the issue by opening WSL Debian in Cmder and running nvim, then compare the displayed output with the attached image while narrowing down whether the problem is in terminal rendering or the WSL/Neovim environment. Done means the cause is identified and the incorrect output no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, neovim
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100