Skip to content
New issue

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

Neovim not working properly in cmder #2583

Closed
2 of 3 tasks
17Swagat opened this issue Aug 12, 2021 · 4 comments
Closed
2 of 3 tasks

Neovim not working properly in cmder #2583

17Swagat opened this issue Aug 12, 2021 · 4 comments

Comments

@17Swagat
Copy link

Purpose of the issue

  • Bug report (encountered problems/errors)
  • Feature request (request for new functionality)
  • Question

Version Information

Cmder Version: 1.3.18.1106

Windows Version: Windows 10 Pro Version: 10.0.19043 Build 19043

Description of the issue

I'm using Neovim as my text-editor and it is not working properly in cmder. All the visual aspects (from plugins and basic neovim configuration) are not appearing. For example: The colorscheme, syntax highlighting. Also sometimes texts seems to broken like in the given images. Even though features of plugins that do not involve visuals seems to be working fine, like coc-explorer, coc- code completion, floaterm are working fine (not visually).

On the other everything is working fine when I run neovim from cmd.

  • Neovim in cmder (Things that are not working fine or behaving abnormally):

cmder_nvim_1

cmder_nvim_2

cmder_nvim_3

  • Neovim in cmder (Things that are working fine):

cmd_nvim_3

cmd_nvim_4

cmder_nvim_4

  • Neovim in cmd:

cmd_nvim_1

cmd_nvim_2

1

2

Although vim that comes with Cmder is working normally. (Following Exactly what I've written in its .vimrc file)
vi

@chrisant996
Copy link
Contributor

Probably it's a matter of setting the terminal info environment variables correctly.

The issue is between ConEmu and neovim, so search on the internet for "ConEmu neovim" to find information about using them together.

ConEmu is the terminal program used by Cmder.

@stale stale bot added the 👀 Awaiting Response Waiting to hear back from the issue reporter. label Apr 16, 2022
@NarrowCode
Copy link

If anyone else is having similar issues, and until the new build referenced here is released - I resolved the issue by adding the following into my Settings > Startup > Environment:

set TERM=conemu

@stale stale bot removed the 👀 Awaiting Response Waiting to hear back from the issue reporter. label Apr 27, 2022
@ggrzybow
Copy link

ggrzybow commented Sep 14, 2022

@NarrowCode It has caused folded lines in Neovim to have a gray background, so I guess some rendering problem got fixed.
Unfortunately I still have corruptions when for example, folding and unfolding functions. For example, before folding the function line says:

225 #endif

After folding the entire function, the line should be empty (showing an empty line between some other folded functions), but it shows:

2       if

An additional side effect is that previously, scrolling up or down (so that some new line goes into view) would solve the rendering artifacts. Presumably, the whole screen was redrawn. But after changing TERM from default cygwin to conemu, scrolling does not fix artifacts, only lines that go out of the view and come back (and thus get fully redrawn) are fixed.

EDIT: Additionally, that envvar change causes delta to print WARNING: terminal is not fully functional and scrolling long diffs (with latest less as a pager) with arrows is not possible (escape codes are inputted as text instead).

@ggrzybow
Copy link

ggrzybow commented Oct 25, 2022

I just updated to Cmder v1.3.20 and the issues described in my previous comment don't happen anymore, probably because TERM is now unset. As a bonus, it seems that Neovim now supports more than 16 colors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants