Add CLI cheatsheet script

[hasecilu]

Description

CLI cheatsheet.

Requirements / Checklist

• Read the Contributing Guidelines
• I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan.
  Issue number where discussion took place: #xxx
• If this contains a font/glyph add its origin as background info below (e.g. URL)
• Verified the license of any newly added font, glyph, or glyph set. License is: xxx

What does this Pull Request (PR) do?

Adds a script that let users to search for an icon using its name using the NF library scripts.

How should this be manually tested?

$ ./cheatsheet divider
       e0b0    i_pl_left_hard_divider
       e0b1    i_pl_left_soft_divider
       e0b2    i_pl_right_hard_divider
       e0b3    i_pl_right_soft_divider
       e0d7    i_ple_left_hard_divider_inverse
       e0d6    i_ple_right_hard_divider_inverse

Any background context you can provide?

There are times when I want to look for a glyph but using the online cheatsheet tool takes "a lot of time". The tool is not slow I mean the whole workflow.

[hasecilu]

To fix the shellcheck fail we can update the hook to use -x flag to let it access external files shellcheck -x cheatsheet.sh or add a config file. docs

[Finii]

Thanks! Excellent!

[Finii]

Ah, added also these commits:

66ae03d shellcheck.sh: Unify variable style
d294607 cheatsheet.sh: Make CWD independent

[Finii]

This (again) reminds me that glyphnames needs a mechanism for aliases, so that in some far future we can drop the i_ files and instead work with the json 'database'.

[Finii]

What is redundant ?! 🤔

🙄

Whatever...

But this is a bug 😨

[hasecilu]

This (again) reminds me that glyphnames needs a mechanism for aliases, so that in some far future we can drop the i_ files and instead work with the json 'database'.

Yeah, I also was thinking on creating sets of glyphs that serve the same purpose, maybe adding tags to database.

For example if you need decorators for a line bar, there are at least 3 terms for decorators: _ple_, divider, separator. So creating a set containing all of them would facilitate to find some you like.

For example on nvim-web-devicons there are 3 sets for: OS, DE and WM. link.

Maybe another relevant sets could be "Programming Languages" which could overlap with "Filetypes", "Git", "Weather", "Animals", etc...