We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cmder version: 1.3.20.151 Operating system: Windows 10
Cmder Full (with Git)
So, I'm a Windows Terminal who migrated to Cmder for some reasons. When I try opening Neovim, the output is just weird.
nvim
The text was updated successfully, but these errors were encountered:
Can you describe specifically what is "weird"?
Sorry, something went wrong.
Probably the same issue as #2583?
Check for the TERM env var, if it's set to anything please post it here.
TERM
@UrNightmaree if you are running WSL you are not running Cmder. You are running WSL in Conemu.
Cmder is a set of settings and tools including Conemu as the terminal emulator that makes cmd.exe and powershell.exe shells more useable.
If you are running a WSL::debian task you are not using any Cmder configuration just Conemu to show the WSL terminal.
Probably the same issue as #2583? Check for the TERM env var, if it's set to anything please post it here.
It's xterm-256color
xterm-256color
No branches or pull requests
Version Information
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
nvim
.Additional context
Checklist
The text was updated successfully, but these errors were encountered: