ryanoasis / nerd-fonts

Iconic font aggregator, collection, & patcher. 3,600+ icons, 50+ patched fonts: Hack, Source Code Pro, more. Glyph collections: Font Awesome, Material Design Icons, Octicons, & more
https://NerdFonts.com
Other
53.84k stars 3.63k forks source link

Roboto has blank or missing glyphs for borders (used in vim's which key, telescope, terminal fuzzy finders in general) #1128

Closed digidoor closed 1 year ago

digidoor commented 1 year ago

🗹 Requirements

🎯 Subject of the issue

Experienced behavior: No borders. roboto

Expected behavior: Borders. 2023-02-18 14_15_49-npm install types-registry@latest

Example symbols: I don't know the codepoint for these non-text glyphs. The fastest way to see these borders for me is to open helix (text editor) and use <Space> to get a little context menu. This is the same border that is used in neovim's telescope plugin, and I believe vim and neovim's which key plugins, so those would also work. The working screenshot is Iosevka and all other Nerd Fonts I've tested work except for Roboto.

🔧 Your Setup

★ Screenshots (Optional)

2023-02-18 15_43_44-npm install types-registry@latest

Finii commented 1 year ago

Thanks for reporting this.

Nerd Fonts does not patch in the border glyphs. Either the font did have them to start with, or they will also not be in the patched font.

But fear not, others also noticed the problem

and because it (that we do not touch them) proses possible problems (whatever, the details are not important here), we have this:

I guess that it will be incoporated in the next days and will then be part of v3.0.0.

If you need the font earlier, you can patch with the patcher from the PR branch, or wait until it has been merged and then use the docker or zip archive to self-patch (which is easier than patching from a branch).

digidoor commented 1 year ago

I guess that it will be incorporated in the next days and will then be part of v3.0.0.

That's fantastic news. I look for ward to it.

github-actions[bot] commented 1 year ago

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference.