-
Notifications
You must be signed in to change notification settings - Fork 498
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
config.toml setting for specifying fallback fonts #2240
Comments
You can also specify fallback fonts in [font]
normal = [ "Symbols Nerd Font Mono", "FiraCode" ] Sorry for the document of this feature is not clear. |
Ah, It's an issue about parsing these configurations. Please try #2244. It seems work now! |
* swap item order in enum, fix: #2240 * add more test cases
It seems that even in Is that intentional? I use the same vim/neovide config across all my machines, and don't necessarily have my preferred fonts set up on all of them, and my preferred pre-installed font depends on the OS. So the "silent fallback" behavior was very convenient for me. |
Is your feature request related to a problem? Please describe.
Neovide previously enabled users to set up fallback fonts for CJK characters, emojis, etc. within the
init.lua
file undervim.o.guifont
. This was achieved by specifying fallback fonts after the default fonts. For instance, an example setup would bevim.o.guifont = "consolas, Noto_Color_Emoji:h11"
, indicating a fallback to the Noto Color Emoji font for character sets not available in Consolas.However, with the release of Neovide 0.12.1, users now have the ability to configure fonts and font features in the
config.toml
file. While this enhancement is a great addition to Neovide, it currently lacks the capability for users to establish fallback fonts to accommodate diverse requirements.Describe the solution you'd like
Add an option to specify a fallback font in config.toml file
Describe alternatives you've considered
I think support for fallback fonts in config.toml would be best for symmetry
The text was updated successfully, but these errors were encountered: