-
-
Notifications
You must be signed in to change notification settings - Fork 146
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
Font rendered very blurry -- maybe scaling issue? #1124
Comments
Yep, that does sound like a scaling issue - very probably the same as #972 and #869. Problem is, I can't reproduce it, so I can't fix it :/.
The command bar is vertically and horizontally centered, that's why it doesn't necessarily align with the grid. I think it's great that way - it makes the fact that it's a separate UI element obvious. |
What desktop are you using? You should be able to run |
Oh, I though the command bar would be aligned to the bottom as in regular neovim. Why does it get centred? |
Yes, I am running sway. Changing the scale of a screen (
Neovim's UI protocol lets UIs decide whether they want to render the command line themselves or let Neovim do it. By default, Firenvim renders the command line itself as this saves a line of screen estate, which is important because the textareas Firenvim operates on are frequently just a few lines tall. If you would rather have neovim render the command line, set the cmdline setting to |
Scale Can you try |
|
This issue probably has been fixed by the merge of #1385. Let me know if the problem persists and I'll re-open. |
#1385 sounds like it's a fix for the issue. I'll set up firenvim again and give it a shot. |
What I tried to do
Using firenvim on Linux (with desktop scaling to 1.5x, which I suspect must be related).
What happened
Text renders very blurry and very large. The blurriness is a bit hard to compare due to how screenshots get compressed:
Firefox+firenvim on the left, neovim on alacritty with font size 11 on the right.
I also noticed that the command bar is misaligned, which is what actually makes me thing this might be related to desktop scaling somehow.
The text was updated successfully, but these errors were encountered: