[why]
There are cases that I find myself into sometimes when I have the glyph
with me but not its name or codepoint. It would be nice to be able to
search for the codepoint and/or name of a glyph by literally putting it
into the search box of the cheat-sheet.
There are several reasons to know the name of the glyph, to use it in a
webpage, to look for alternatives when they get removed, etc.
[how]
Convert high codepoint-chars to codepoint text.
Fixes: #1307
Authored-by: ad-chaos
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
The additional hints in the bottom are hard to notice if we flood users
with all available items first.
Usually users want to search the icons and not browse, so showing them
all per default seems better.
[how]
Just do not change the search term from "" to something else, so the
search comes up empty on an empty search.
If people search for a blank the previous mechanics to show all icons is
triggered instead. A message to hint for this is added to the empty
search result.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
* We want to have the autocreated cheat-sheet file here 100% and not
only approximate, so create the file anew via generate-css.sh and
commit it here.
* "No results found" is kind of a lie, we have a result and the result
is that there are no hits while searching :-> Call me pedantic.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Often it is easier to find what one wants if the search result is
sorted.
[how]
Do a full result sort.
* Sort by id (class name)
* Put removed icons last
We do not need the boost function anymore, so that pre-sorting is
removed.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
Sometimes one does not know what the exact search term is.
For example if you want to find a 'homefolder' but the name is
'homedirectory' it is impossible to find.
[how]
Allow prefix search, in this case at least 'home' will find both
variants.
I do believe a full substring search would be even better, but that is
not supported by minisearch.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
[why]
After the last bullet point closing the <div> seems problematic and
results in a bit of garbage in the html page.
[how]
Just use the dashes as we historically used instead.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
I think the `</div> </details>` at the end of the v3.0.1 release notes was being parsed as part of the last `<li>` item, resulting in `</div> </details>` being escaped. This commit should fix the issue where in the HTML output, the v3.0.1 release `<details>` included the release notes for v3.0.0, v2.3.3, etc.
[why]
There are 2.9 rows of icons shown.
This looks rather odd, with the last (3rd) row having their bottoms
removed.
[how]
Show instead 3.1 rows. This gives a visual hint to the user that
scrolling is possible (because the tops of the 4th row are shows), and
looks better with only 3 rows.
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
This step adds just the stuff generated via script in the master branch.
See pairing commit in the gh-pages branch:
Date: Wed May 3 17:54:44 2023 +0200
generate-css: Create cheat sheet with removed icons
Signed-off-by: Fini Jastrow <ulf.fini.jastrow@desy.de>
Update the cheat sheet to v3.0.0 but also show the removed icons of
v2.3.3. That style is .nfold (read: nf-old) and it is just hacked in.
I believe it can be removed later on, with 3.1.0 or something at least.
We also need the old (removed) icons as a font to display them despite
being removed. A small helper script 'archives' just the dropped glyphs
into a new webfont.
The script can be removed afterwards, this is a single run, archiving
the dropped after v2.3.3 icons.
See pairing commit in master branch:
Date: Wed May 3 17:54:44 2023 +0200
generate-css: Create cheat sheet with removed icons
[note]
Also remove unused `nerd-fonts-generated.css`, wich confuses me every
time. It's sufficient to have it in the master branch for people, we do
not use it here.
f
