Shell variables with established names for icons

[powerman]

I've gathered established names for all icons from many places and created https://github.com/powerman/nerd-fonts-sh to make it easier to use icons in shell scripts. In case there are several established names - I've provided aliases.

It may make sense to merge these files into your repo - this should make it easier to keep them in sync with font changes. If you'll do this - I'll close my repo. If you don't wanna merge them - you may like to add link to my repo.

I was unable to find established names for some icons (16 for Powerline Extra Symbols, 5 for Custom and 8 for Devicons), I suppose it's mostly for icons you've added on your own. So, if you know names for them - please send me PR. :)

[ryanoasis]

@powerman That's just... awesome 🎉

I would ❤️ to see this in the Nerd Fonts repo 😊

---

Yeah the powerline extra symbols I didn't give official names (can work on that) and yes there were some other custom ones added. On Devicons not sure why some might not have.

If you want I can try to add this to the next release (1.1) I just haven't spent much time on dev 😢 so maybe this weekend I can get a preliminary branch together for 1.1 😄

---

This is not exactly related but I am working on a test script that will print out the glyphs but that is mostly for testing the font after patching where these scripts you mention are more for use in scripts (like you mentioned). Nevertheless here is some preview:

(WIP)

[powerman]

If you like I can push these scripts, but let me know which directory/names I should use. I'll open PR to let you review, of course.

[ryanoasis]

If you would like to create a branch here go for it you have my blessing 😄 (just please not master -- though I don't think you can).

I will create a 1.1 branch this weekend I believe

I think in bin/scripts makes sense but maybe there could be another sub-dir there.. I am not 100% sure. I will think about it some more.

[ryanoasis]

Closed with PR #147

[github-actions]

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.