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

Vim in Lilyterm #130

Open
haldbusfumblecore opened this issue Jun 16, 2018 · 3 comments
Open

Vim in Lilyterm #130

haldbusfumblecore opened this issue Jun 16, 2018 · 3 comments

Comments

@haldbusfumblecore
Copy link

Hello! Really like Lilyterm. I have started to theme my Vim and run into problems. If I understand it correctly the default for Lily is 256-colors when emulating Xterm with the same support, though it doesn't seem to lay out properly at all. Also there are some problems loading plugins. How to I troubleshoot this? Have camped Google both yesterday and today looking for answers.

Running FreeBSD 11 with latest Lilyterm.
I provide with a picture comparing it to Xterm (left) and Lily (right):
vim_on_xterm_vs_lily

Thank you for you help.

Best wishes,
haldbusfumblecore

@anselal
Copy link

anselal commented Jun 21, 2018

Try setting TERM=xterm-256color in your .bashrc file or in your .profile file

@miker
Copy link

miker commented Jun 29, 2018

That almost looks like a font issue. What font are you using in LilyTerm?

@haldbusfumblecore
Copy link
Author

Hello again. I have done some settings and I have tried going with TERM=xterm-256color. The result is having Lilyterm to fail to emulate at all == only being black.

Running SpaceVim in terminals I know have truecolor support (forementioned xterm and sakura) ends up in correct colour display.

Can display colours in Lilyterm when turning truecolor off, setting
enable_guicolors = false #defaults to true
in ~/.SpaceVim.d/init.toml

The problem is that my Lilyterm doesn't have truecolor support, but will have if compiled with vte 0.36 through this fix:
72536e7

I'll compile it manually because the version from FreeBSD ports seems to not offer this by default.
The issue should be solved by then.

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

No branches or pull requests

3 participants