-
Notifications
You must be signed in to change notification settings - Fork 3
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
Vertical alignment issue with splits, impacted by font weight setting #60
Comments
Thanks for your very detailed report and your thoughts on eovim, I really appreciate ;) The text widget I use in eovim enables rich text rendering, such as ligatures, easy line spacing, and fancy underlines. Since it is not a "matrix of glyphs", it absolutely requires that all glyphs have the same width. I ran on the exact same problem with a I think that the problem here is caused by the bold font. I'm not sure what happens exactly, but when Can you please check if |
Interesting. Your explanation certainly makes sense, however I do have Fira Code Bold installed. I'm on Fedora 32 so I simply installed the fira-code-fonts package:
I have Fira Code Bold installed:
Here is the output of
|
One other unrelated side issue that is probably simple to resolve, but I don't know much vimscript, is that in order to make eovim work properly with colorschemes I have had to put The only downside of this is now the colorscheme doesn't load properly if I just happen to run nvim within my rxvt terminal, probably due to lack of true color support or so, or something else. Setting my $TERM made no difference. I don't use nvim directly in the console that much (I use eovim!), but sometimes it is handy just for a super quick edit, and so having all the nice colours disappear is slightly annoying although no big deal. I suppose I could switch terminals, to something like kitty, but I rather like the efficiency of rxvt-unicode. It works fine in rxvt without the
So that basically the Thanks! :-) |
Okay... interesting. I'll investigate the font issue more into details. Thanks for the info. For setting if exists("g:eovim_running")
set termguicolors
endif If you are interested in more vim scripting, there is a Wiki page that explains some tricks. |
eovim --version
: 0.1.3.99-69652c1nvim --version | head -n1
: NVIM v0.4.3edje_cc --version
: Version: 1.23.Hello
Thanks for your work on this. It is definitely one of the best Neovim front-ends. The simple addition of the floating command palette makes a massive difference in these days of high-res/large screens.
One issue, however. I have noticed that vertical splits seem to have an alignment issue, possibly/probably related to the ligature (?) support, and in particular triggered by
NERDTree
.As recommended, I installed Fira Code, which looks great. If I set the font to use any of the different font weights (e.g. style=Medium), the problem with vertical alignment is 10x worse.
If I just use plain Fira Code with no style option specified as my
guifont
, the problem is essentially almost non-existent; I say "almost", because when I toggle NERDTree, a couple of vertical bars are very slightly misaligned, e.g. by just a couple of pixels, far less dramatic than the screenshots below. This misalignment propagates to any other split views in the window. However, it immediately disappears and all is perfect again as soon as I close/toggle NERDTRee back to hidden.So in practice it is only the tiniest imperfection and does not impact usability, it is more of a slight aesthetic ugliness issue.
With, say, Fira Code using the medium style option to increase the font weight, the problem is much more serious. Even after toggling NERDTree to close again, the vertical misalignment remains between splits, which is very ugly. So it essentially makes alternative font weights very problematical.
As I say, my guess is this is related to way that
eovim
is handling ligatures or some other font width metric.Hopefully the attached screenshots will explain it better than my text above does.
The text was updated successfully, but these errors were encountered: