-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Text list of nerdfont characters #448
Comments
Hey, at first I was going to suggest https://github.com/ryanoasis/nerd-fonts/blob/master/bin/scripts/test-fonts.sh but that isn't for parsing just a formatted visually grep-able table. https://github.com/ryanoasis/nerd-fonts/blob/master/bin/scripts/lib/i_all.sh is probably the closest script to get a list of characters but probably still not quite what you're looking for but likely needs to be tweaked as it's mostly a convenience for having variables represent the glyphs |
I was looking for this as well. I couldn't find it so I made a quick script that parses the files mentioned above and outputs a nicer file with just the icon and the name of the icon. I posted it at https://gitlab.com/dmease/nerd-font-dmenu. You can generate the file yourself, or just grab |
Done again at https://gitlab.com/jake.gillberg/nerd-fonts-glyph-list formatted like:
|
Wrote a quick dirty script by parsing the css: https://nerd-fonts-glyph.deno.dev If it's failing just ping me. (p.s. don't except much code quality, it's only 5 minutes of script-fu) |
?! Reminds me of #1059 (comment) The next comments have the commands how to create the lists. Very easy. What do you need? |
Hey @Finii, I changed it to return the glyphs directly. I'm wondering can we have a list (preferably csv) in the repository or in the releases? Currently the only stable way to do that is parsing the scripts in |
@mochaaP Creating such a list is very easy for Nerd Fonts (*). We just need to define how it shall look like. It can then be autocreated by the CI on any changes and be part of the Release packages. Must admit did not read all the text above very carefully. Just define some format all people can live with. And then I also like Looking on the original poster above the UNIDATA list looks like this
Hmm, colon separated values ;-)
I'm not sure if putting the glyphs directly into the file is a good idea 🤔 Otoh we have it in the (*) I mean, we autocreate everything from the names stored in the font files: |
Is this a good format an data?
What would be the name for that list in the repo? Where to put it? |
@mochaaP Hmm, I believe your list at https://nerd-fonts-glyph.deno.dev/ is wrong? The 5 hex-digit Copy and pasted from the Or here: Edit: |
Thanks for the feedback! On it. |
If you like we can put your generator into this repo and activate a workflow for it so that it is always automatically updated. |
[why] Somebody might want to have a file where all symbols we add are listed. At the moment there are only the i_*.sh scripts and the CSS files. Both are rather unwieldy. [how] Just create a json file with all symbol names, like the CSS file. Fixes: #448 Signed-off-by: Fini Jastrow <[email protected]>
[why] Somebody might want to have a file where all symbols we add are listed. At the moment there are only the i_*.sh scripts and the CSS files. Both are rather unwieldy. [how] Just create a json file with all symbol names, like the CSS file. Fixes: #448 Signed-off-by: Fini Jastrow <[email protected]>
The changes to the CSS script are so simple, I just added writing a json to that script. |
Glad to hear that! 😀 |
Note that I dropped the |
[why] Just having the characters themselves as data for the name is convenient in some cases; but sometimes the codepoint is also nice. And it certainly improves the human interaction / check of the file. [how] Include the character and the codepoint in the glyph-name data. This is a breaking change. But given that the json file is rather new I believe we can get away with it. Sorry for the inconvenience for all the early adaptors that already use the old/previous format. But now we are more future proof and can add even more data without breaking old json code. Related: #1140 kovidgoyal/kitty#2972 chrisbra/unicode.vim#39 #448 nvim-tree/nvim-web-devicons#192 Signed-off-by: Fini Jastrow <[email protected]>
[why] Just having the characters themselves as data for the name is convenient in some cases; but sometimes the codepoint is also nice. And it certainly improves the human interaction / check of the file. [how] Include the character and the codepoint in the glyph-name data. This is a breaking change. But given that the json file is rather new I believe we can get away with it. Sorry for the inconvenience for all the early adaptors that already use the old/previous format. But now we are more future proof and can add even more data without breaking old json code. Related: #1140 kovidgoyal/kitty#2972 chrisbra/unicode.vim#39 #448 nvim-tree/nvim-web-devicons#192 Signed-off-by: Fini Jastrow <[email protected]>
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. |
[why] Somebody might want to have a file where all symbols we add are listed. At the moment there are only the i_*.sh scripts and the CSS files. Both are rather unwieldy. [how] Just create a json file with all symbol names, like the CSS file. Fixes: ryanoasis#448 Signed-off-by: Fini Jastrow <[email protected]>
Is there a full list of all nerdfont characters available similar to http://www.unicode.org/Public/UNIDATA/UnicodeData.txt? I'm looking for something that could be used with Unicode.vim. See chrisbra/unicode.vim#39.
The text was updated successfully, but these errors were encountered: