From bc374ce62bb5918dc8d55808d6662e83d368c6bb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?George=20Guimar=C3=A3es?= Date: Fri, 20 Oct 2023 14:53:40 -0300 Subject: [PATCH 1/7] Add Neovim icon and run generate-original-source.py --- bin/scripts/lib/i_seti.sh | 5 +- src/glyphs/original-source.otf | Bin 151764 -> 152428 bytes src/svgs/icons.tsv | 1 + src/svgs/neovim.svg | 82 +++++++++++++++++++++++++++++++++ 4 files changed, 86 insertions(+), 2 deletions(-) create mode 100644 src/svgs/neovim.svg diff --git a/bin/scripts/lib/i_seti.sh b/bin/scripts/lib/i_seti.sh index 47dd87d9bb..85795139a6 100644 --- a/bin/scripts/lib/i_seti.sh +++ b/bin/scripts/lib/i_seti.sh @@ -1,6 +1,6 @@ #!/usr/bin/env bash -# Seti-UI + Custom (180 icons, 19 aliases) -# Codepoints: E5FA-E6AD +# Seti-UI + Custom (181 icons, 19 aliases) +# Codepoints: E5FA-E6AE # Nerd Fonts Version: 3.0.2 # Script Version: (autogenerated) test -n "$__i_seti_loaded" && return || __i_seti_loaded=1 @@ -203,4 +203,5 @@ i='' i_seti_zip=$i i='' i_custom_asm=$i i='' i_custom_v_lang=$i i='' i_custom_folder_oct=$i +i='' i_custom_neovim=$i unset i diff --git a/src/glyphs/original-source.otf b/src/glyphs/original-source.otf index 2d5c31c3857d270b028e5fbe2fc735d4b39e29ef..e4b8c494f98beca76bf9146253dbabf181754209 100644 GIT binary patch delta 1842 zcmXw233N2iAhO` z&_jV2488mHGnOYP2LbQF5dHTh4(n`A{%6E#fWW_T>Dg)19*+!f3TWm7;%H_@+W1x{ zjAOXAh5y|$dBc0XR|WG@{)cB~=gbK|8`c+Mh?{%lWT(xU2IpWdf!EMYNz0DQ7&1L? z02jvrUQMP=oslD*=)wU^EHKv0^#TTzRXt1%=Jjf!_^p+QsbT9X`FXlX?)*CB+?)pB375fQc@D5A@B%;6&-jh=l`)Vh{y;X?~* zxejJpUCVtjh;G?hi|cwbOo%`vOg7;at2LVLLIJ1R@Ca5RCe0fQD#< z5Hv;;o)(H`2!qjz=4gSI2uCZlMjNz6JG4g!bmX+1(3w+5!ptZA9=f6%x+4nFh(RoR zpeNqP2e2Rxz0ezd&=>viAwEJp`eOhFA_0Sth`|_wp%{iFBx5*6U?fIiG{#^oK1K>s zVI7Awe1de0M+PQfA~G=vpJFnykc}yrifQ-^(=h`%n2A}K&Bs3%pJN{8V*wVz%5UT% zEXERifu&f6Tr9^5e2F~dVhtTM#nYp{`!DPsp&IkoebS{Fc*%6&`u zb7q@reY_$oQK(1}fS@?SdrhR)ol(#3Q=mu>{m z%|3LifXbdwc{JVIL=TGSQ6N1jr{@#M-J9HpC{Cu4tQ6v~(C!f4RibWt5gT9Rm+CL%hDPMM;!S(tB&?w3V$f{1pD7>DC|@OO6`@`rLw;g2TQC97|k zA*&BwL|$GU$0>IdHRt_!s0tOF;N?0C7x`MQNV!#Kad=)|x!|YNm$JHCEe9#~>)%sY zSBsP{U$Ck2l8c=cDm>!>drK|SQ+7(p%agJySdr2_z#^rmHN(pr7JG9S85?pJSQr{J z>}$YIVNhq<6I>LQ?9xeS6OhN)Or3X@L35LVGF){e-49nJ@)c+$>Q<_yB$tF=G;jL! zWzc2v(tkggr7);W$`=-UiHqtDwL*%uj}T|R`?BXxR?pHz~EcE=?RZT=Di#@W0f+H2a`&Yr-^z~f^ z_dM|OG&9c~h4V<&tl zn{q$e&i!TFbEaq9tgmiZ&mys{I+kUI2QCTYa7ChJ6E=9t3pvoyn+h9dkK+2wmymR? aSdpHPKiI!KgO$t2yR^>LgG3)eOaB8*H)bdR delta 1208 zcmXw#3rv+|7{{Ogdv1K3bGU^hQxF^pBW^ns0-7G;l0XV2*yfhWl8u@Wi5Z2-@s@=+ z#e=bCgs_B0uvMpl=4Bty#nlGcScI;Gz=B4oEaCui-kxKpZ+o8i_dd`6xxC+0t1{TE zROb~Gjov zNpaDxi2Q4}IQIctQV9nP^_nT>LAHpJ(!G@ty`d_Jyq&DyQ(9D6PF?w&A}5=^tf(}t zc(|s&nv*QhEGvJdVz2C`L|))47KA;Rt09VhyRG8|-}SR()N+_;=f`jT9*&?cX3av5YGD7eK3UT{6NvtRru{ z?qNMy@UDlAv;{-mIO;8*{_Ne`%%q8IzNfGblXbLybO2! zgS(cZ_|)?>kf5;Jol^2WY1^VSs*2CKm-rX=ShfgMg(h#g5xB(#t5n6%p z-|&bXF-=JL5|1B6stM~3VM8;lsYt6q+9I-ikX?_bTe0N~w%$Ww9CjS9#>*3^*o`;p z@#YAsva$as9N2|}%{bhTV+I_%f!b|2aT4{@IGc(O$I#M(^DeX|puHIF1L)|(XRo0< z4Hq`z;wfBi!qpQPjKok3e*OYCChLK3~ zVw=!q3Bx&I9uPil!q+VPB85K*f0qc+h}EqkN-turi#W508xocyV(qIUc}Ao(I`#!! z8Z&xH*RYpOx<1WU9h(-C!2zP%HYpp+Y>wu|{;y5yGAUiRiNgVELsbt}JxWskGt2JY z_bQjS^^jZ|=_H+$i-BC|%(Y6nw8kwOwlxg&Ak4%)KYo~_BHF5J(D!0hwM{Qcx0#N! z54CdZUhc2G$qvQb6B7}tq*@#IB%iyC+5&c_6q_XPOeXzHB+1g&u!?O z+Hk8E!B5%b(zlOsH6ei&ONY1xwcD7Icy+ntqq3h1 + + + neovim-1color@2x + Created with Sketch (http://www.bohemiancoding.com/sketch) + + + + + + + + + + + + neovim-1color@2x + + + + From 43eb9a126033d4bbf2f13578ae5f4ea2f07f064d Mon Sep 17 00:00:00 2001 From: Fini Jastrow Date: Mon, 23 Oct 2023 13:15:57 +0200 Subject: [PATCH 2/7] neovim: Improve filename [why] To avoid filename clashes between Seti and Custom we have all Custom files with a _nf suffix. This has not been documented. Signed-off-by: Fini Jastrow --- src/svgs/README.md | 2 ++ src/svgs/{neovim.svg => neovim_nf.svg} | 0 2 files changed, 2 insertions(+) rename src/svgs/{neovim.svg => neovim_nf.svg} (100%) diff --git a/src/svgs/README.md b/src/svgs/README.md index 6ea6e817b0..6b555dca05 100644 --- a/src/svgs/README.md +++ b/src/svgs/README.md @@ -2,6 +2,8 @@ These are the source glyphs for the 'Seti and Original' icon set. +Files for the 'Original' set have a `_nf` suffix to avoid any mixup with the Seti filenames. + `generate-original-source.py` generates a font file from all these individual glyphs. That font is then used for the actual patching process. The codepoints and names of the icons here have to be put into `icons.tsv`. diff --git a/src/svgs/neovim.svg b/src/svgs/neovim_nf.svg similarity index 100% rename from src/svgs/neovim.svg rename to src/svgs/neovim_nf.svg From 7bceb83919608e1c53618ede3bb2422f2f7dd90e Mon Sep 17 00:00:00 2001 From: Fini Jastrow Date: Mon, 23 Oct 2023 13:17:56 +0200 Subject: [PATCH 3/7] doc: Improve contributing manual Signed-off-by: Fini Jastrow --- contributing.md | 63 ++++++++++++++++++++++++---------------------- src/svgs/icons.tsv | 4 ++- 2 files changed, 36 insertions(+), 31 deletions(-) diff --git a/contributing.md b/contributing.md index 69300bc47d..e2820f38a5 100644 --- a/contributing.md +++ b/contributing.md @@ -4,23 +4,28 @@ ## How to contribute summary +Often it can be helpful to discuss a PR first in an Issue to avoid later problems or re-design when it is in review. + * Fork the project and submit a Pull Request (PR) * Explain what the PR fixes or improves * Screenshots for bonus points * Use sensible commit messages - * If your PR fixes a separate issue number, include it in the commit message + * Short descriptive title in the first line, one empty line, and then multiple lines with an explanation (why and how). + * If your PR fixes a separate issue number, include it in the commit message like `Fixes: #123` (on a separate line). * Use a sensible number of commit messages as well * e.g. Your PR should not have 100s of commits - + * If you fix a previous commit of the PR it might be worth considering to squash them + ## How to add yourself to the contributors (give yourself attribution) Don't forget to give yourself credit! Make sure you add yourself to the contributors list that will eventually propagate to [NerdFonts.com](https://nerdfonts.com) +Usually the person pulling your PR will make sure you did not forget this step. Either: * Invoke the [@all-contributors bot](https://allcontributors.org/docs/en/bot/usage) by commenting on your Pull Request or Issue. -* Shallow clone repo and execute `all-contributors add ` +* _(not advised)_ Shallow clone repo and execute `all-contributors add ` -Common types for this project include: `code`, `doc`, `translation`, `review` .For full list of contribution types see: https://allcontributors.org/docs/en/emoji-key +Common types for this project include: `code`, `doc`, `translation`, `review`. For full list of contribution types see: https://allcontributors.org/docs/en/emoji-key ## Steps for updating an existing font @@ -28,47 +33,44 @@ Common types for this project include: `code`, `doc`, `translation`, `review` .F * Copy and replace the existing unpatched version of the font and any readme and/or license files in the `src/unpatched-fonts/XYZ-font` directory * e.g. Updating *XYZ Font*, update files in directory `src/unpatched-fonts/xyz/{PUT FONT FILES HERE}` * Make sure to update the correct subfolders for each font style (e.g. `src/unpatched-fonts/xyz/bold/{BOLD FONT FILES HERE}`) + * Update version information in the `readme.md` file(s) + * Add all the modifications into a git commit. ### 2. Execute basic testing * Do a basic test with the new font to ensure it patches correctly and generates a new font file, e.g. - * `fontforge --script ./font-patcher src/unpatched-fonts/XYZ/XYZ.ttf --complete` - * Make sure to then delete this new font file if it is in the repository (all patched fonts should be generated in the `patched-fonts` directory) + * `fontforge --script ./font-patcher src/unpatched-fonts/XYZ/XYZ.ttf --complete --debug 2` + * Make sure to then delete this new font file if it is in the repository ### 3. Run build scripts -* When fairly satisfied the font patches correctly, run the following scripts in this order: - * Copy all the unpatched readmes to the patched location with additional info on variations appended: - * `cd bin/scripts` - * `./standardize-and-complete-readmes.sh XYZ` +This is not needed and you should never commit any patched files directly to the repo. The Github workflow will do that at appropriate times. + +* When fairly satisfied the font patches correctly, run the following: * Patch **all** of the variations/options, e.g. - * `./gotta-patch-em-all-font-patcher\!.sh XYZ` + * `./gotta-patch-em-all-font-patcher\!.sh /XYZ` ## Steps for adding a new font or removing an existing font -* For removal of a font skip to [Step #4](#4-run-build-scripts) - ### 1. Verify license * Check the license even allows the font to be modified and shared ### 2. Add original (unpatched) version -* Add the unpatched version of the font and any readme and/or license files to the `src/unpatched-fonts/` directory inside a new directory +* Add the unpatched version of the font and any license files to the `src/unpatched-fonts/` directory inside a new directory * e.g. Adding *XYZ Font*, create directory `src/unpatched-fonts/xyz/{PUT FONT FILES HERE}` * Try to make subfolders for each font style (e.g. `src/unpatched-fonts/xyz/bold/{BOLD FONT FILES HERE}`) + * Add a `README.md` file to `src/unpatched-fonts/xyz` that follows the style of the existing fonts. + * If the font has Oblique instead of Italic, set that (and other specials) in the `config.cfg` file + * Update information in the `/readme.md` file(s) + * Insert font into `bin/scripts/lib/fonts.json`; use repoRelease=false + * Add all the modifications into a git commit. ### 3. Execute basic testing * Do a basic test with the new font to ensure it patches correctly and generates a new font file, e.g. - * `fontforge --script ./font-patcher src/unpatched-fonts/XYZ/XYZ.ttf --complete` + * `fontforge --script ./font-patcher src/unpatched-fonts/XYZ/XYZ.ttf --complete --debug 2` * Make sure to then delete this new font file if it is in the repository (all patched fonts should be generated in the `patched-fonts` directory) ### 4. Run build scripts -* When fairly satisfied the font patches correctly, run the following scripts in this order: - * Copy all the unpatched readmes to the patched location with additional info on variations appended: - * `./standardize-and-complete-readmes.sh` +* When fairly satisfied the font patches correctly, run the following: * Patch **all** of the variations/options, e.g. - * `./gotta-patch-em-all-font-patcher\!.sh XYZ` -### 5. Update readme -* Add the new font to the table of [Patched Fonts][] -* Update the "counts" in the [Features Section][] - * You can get this information by simply passing a second param to the "all patcher": `./gotta-patch-em-all-font-patcher\!.sh "" info` - * "`X` already patched font families" -> Give exact number from 'typefaces' line - * "Over `X` unique combinations/variations..." -> round down to nearest hundred from 'variation' line - * "Over `X` glyphs/icons combined" -> manual process for now (@todo) -* Update the "counts" in the [Combinations Section][] - * Again, get this info from the "all patcher" + * `NERDFONTS='--debug 2 --makegroups 1' ./gotta-patch-em-all-font-patcher\!.sh /XYZ` + * If there are name length problems you might want to add `--makegroups 2` or increasing (3, 4, ...), until all fonts of the set come out without error. + To increase testing speed add `--dry` to the `NERDFONTS` variable above. + * Add the needed `makegroups` level (if it is not 1) to the `config.cfg` file and ammend your commit. +### 5. Release ## Things to keep in mind @@ -88,8 +90,9 @@ Common types for this project include: `code`, `doc`, `translation`, `review` .F * Squashing to 1 commit is **not** required at this time * Use sensible commit messages (when in doubt: `git log`) -* Use a sensible number of commit messages -* If your PR fixes a specific issue number, include it in the commit message: `"Fixes XYZ error (fixes #123)"` +* Short descriptive title in the first line, one empty line, and then multiple lines with an explanation (e.g. why and how). +* Use a sensible number of commits +* If your PR fixes a specific issue number, include it in the commit message: `Fixes: #123` as this activates the autolink and autoclose mechanism. ## Code standards diff --git a/src/svgs/icons.tsv b/src/svgs/icons.tsv index 4dee8cc68e..9632c4dc83 100644 --- a/src/svgs/icons.tsv +++ b/src/svgs/icons.tsv @@ -6,7 +6,9 @@ # Keep the numbers consecutive. # You can add aliases by adding a new line with the same offset but # different name; omit the filename on those lines. -# Use generate-original-source.py to regenerate the font used to patch. +# +# The Github workflow will automatically execute +# generate-original-source.py to regenerate the font used to patch. # # offset name (in i_seti.sh) filename (.svg) # From 654855a0671493b8d11328bcebb0fcc560a68ff6 Mon Sep 17 00:00:00 2001 From: Fini Jastrow Date: Mon, 23 Oct 2023 13:27:39 +0200 Subject: [PATCH 4/7] doc: Further contributing information on icon core set Signed-off-by: Fini Jastrow --- contributing.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/contributing.md b/contributing.md index e2820f38a5..8fc1f2fdce 100644 --- a/contributing.md +++ b/contributing.md @@ -71,6 +71,14 @@ This is not needed and you should never commit any patched files directly to the To increase testing speed add `--dry` to the `NERDFONTS` variable above. * Add the needed `makegroups` level (if it is not 1) to the `config.cfg` file and ammend your commit. ### 5. Release +* As we do not release directly to the repository anymore the new font will only be seen on a real release. +* For that the font image preview will also be needed (`generate-font-image-previews.sh`). +* What is automated via Github workflows and what not might change over time, so nothing is specified hereA. + +## Steps to add a new icon to the core set +Codepoints in the code set are a scarce resource, so in general it is unlikely that a icon will be added. +* To add a icon one just needs to throw the svg into the correct directory and add a line to `icons.tsv`. +* The workflow than automagically updates the `i_seti.sh` and the `original-source.otf` (workflow `PackSVGs`). ## Things to keep in mind From 5615d5e12070b26d9be60277231a434272a8d3e2 Mon Sep 17 00:00:00 2001 From: Fini Jastrow Date: Mon, 23 Oct 2023 13:29:40 +0200 Subject: [PATCH 5/7] font-patcher: Increase after new core icon [why] After a new icon has been added to the core set we want to make that visible via a new version number. Signed-off-by: Fini Jastrow --- font-patcher | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/font-patcher b/font-patcher index ba8625144a..9964583b51 100755 --- a/font-patcher +++ b/font-patcher @@ -6,7 +6,7 @@ from __future__ import absolute_import, print_function, unicode_literals # Change the script version when you edit this script: -script_version = "4.6.0" +script_version = "4.6.1" version = "3.0.2" projectName = "Nerd Fonts" From 3d860fbb83f0b8a0f2cf7bafe9661eb3d603d53b Mon Sep 17 00:00:00 2001 From: Fini Jastrow Date: Mon, 23 Oct 2023 13:34:06 +0200 Subject: [PATCH 6/7] Revert: "run generate-original-source.py" [why] We want the workflow to do this so that we have control over the fontforge version that is used. Signed-off-by: Fini Jastrow --- bin/scripts/lib/i_seti.sh | 5 ++--- src/glyphs/original-source.otf | Bin 152428 -> 151764 bytes 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/bin/scripts/lib/i_seti.sh b/bin/scripts/lib/i_seti.sh index 85795139a6..47dd87d9bb 100644 --- a/bin/scripts/lib/i_seti.sh +++ b/bin/scripts/lib/i_seti.sh @@ -1,6 +1,6 @@ #!/usr/bin/env bash -# Seti-UI + Custom (181 icons, 19 aliases) -# Codepoints: E5FA-E6AE +# Seti-UI + Custom (180 icons, 19 aliases) +# Codepoints: E5FA-E6AD # Nerd Fonts Version: 3.0.2 # Script Version: (autogenerated) test -n "$__i_seti_loaded" && return || __i_seti_loaded=1 @@ -203,5 +203,4 @@ i='' i_seti_zip=$i i='' i_custom_asm=$i i='' i_custom_v_lang=$i i='' i_custom_folder_oct=$i -i='' i_custom_neovim=$i unset i diff --git a/src/glyphs/original-source.otf b/src/glyphs/original-source.otf index e4b8c494f98beca76bf9146253dbabf181754209..2d5c31c3857d270b028e5fbe2fc735d4b39e29ef 100644 GIT binary patch delta 1208 zcmXw#3rv+|7{{Ogdv1K3bGU^hQxF^pBW^ns0-7G;l0XV2*yfhWl8u@Wi5Z2-@s@=+ z#e=bCgs_B0uvMpl=4Bty#nlGcScI;Gz=B4oEaCui-kxKpZ+o8i_dd`6xxC+0t1{TE zROb~Gjov zNpaDxi2Q4}IQIctQV9nP^_nT>LAHpJ(!G@ty`d_Jyq&DyQ(9D6PF?w&A}5=^tf(}t zc(|s&nv*QhEGvJdVz2C`L|))47KA;Rt09VhyRG8|-}SR()N+_;=f`jT9*&?cX3av5YGD7eK3UT{6NvtRru{ z?qNMy@UDlAv;{-mIO;8*{_Ne`%%q8IzNfGblXbLybO2! zgS(cZ_|)?>kf5;Jol^2WY1^VSs*2CKm-rX=ShfgMg(h#g5xB(#t5n6%p z-|&bXF-=JL5|1B6stM~3VM8;lsYt6q+9I-ikX?_bTe0N~w%$Ww9CjS9#>*3^*o`;p z@#YAsva$as9N2|}%{bhTV+I_%f!b|2aT4{@IGc(O$I#M(^DeX|puHIF1L)|(XRo0< z4Hq`z;wfBi!qpQPjKok3e*OYCChLK3~ zVw=!q3Bx&I9uPil!q+VPB85K*f0qc+h}EqkN-turi#W508xocyV(qIUc}Ao(I`#!! z8Z&xH*RYpOx<1WU9h(-C!2zP%HYpp+Y>wu|{;y5yGAUiRiNgVELsbt}JxWskGt2JY z_bQjS^^jZ|=_H+$i-BC|%(Y6nw8kwOwlxg&Ak4%)KYo~_BHF5J(D!0hwM{Qcx0#N! z54CdZUhc2G$qvQb6B7}tq*@#IB%iyC+5&c_6q_XPOeXzHB+1g&u!?O z+Hk8E!B5%b(zlOsH6ei&ONY1xwcD7Icy+ntqq3h12iAhO` z&_jV2488mHGnOYP2LbQF5dHTh4(n`A{%6E#fWW_T>Dg)19*+!f3TWm7;%H_@+W1x{ zjAOXAh5y|$dBc0XR|WG@{)cB~=gbK|8`c+Mh?{%lWT(xU2IpWdf!EMYNz0DQ7&1L? z02jvrUQMP=oslD*=)wU^EHKv0^#TTzRXt1%=Jjf!_^p+QsbT9X`FXlX?)*CB+?)pB375fQc@D5A@B%;6&-jh=l`)Vh{y;X?~* zxejJpUCVtjh;G?hi|cwbOo%`vOg7;at2LVLLIJ1R@Ca5RCe0fQD#< z5Hv;;o)(H`2!qjz=4gSI2uCZlMjNz6JG4g!bmX+1(3w+5!ptZA9=f6%x+4nFh(RoR zpeNqP2e2Rxz0ezd&=>viAwEJp`eOhFA_0Sth`|_wp%{iFBx5*6U?fIiG{#^oK1K>s zVI7Awe1de0M+PQfA~G=vpJFnykc}yrifQ-^(=h`%n2A}K&Bs3%pJN{8V*wVz%5UT% zEXERifu&f6Tr9^5e2F~dVhtTM#nYp{`!DPsp&IkoebS{Fc*%6&`u zb7q@reY_$oQK(1}fS@?SdrhR)ol(#3Q=mu>{m z%|3LifXbdwc{JVIL=TGSQ6N1jr{@#M-J9HpC{Cu4tQ6v~(C!f4RibWt5gT9Rm+CL%hDPMM;!S(tB&?w3V$f{1pD7>DC|@OO6`@`rLw;g2TQC97|k zA*&BwL|$GU$0>IdHRt_!s0tOF;N?0C7x`MQNV!#Kad=)|x!|YNm$JHCEe9#~>)%sY zSBsP{U$Ck2l8c=cDm>!>drK|SQ+7(p%agJySdr2_z#^rmHN(pr7JG9S85?pJSQr{J z>}$YIVNhq<6I>LQ?9xeS6OhN)Or3X@L35LVGF){e-49nJ@)c+$>Q<_yB$tF=G;jL! zWzc2v(tkggr7);W$`=-UiHqtDwL*%uj}T|R`?BXxR?pHz~EcE=?RZT=Di#@W0f+H2a`&Yr-^z~f^ z_dM|OG&9c~h4V<&tl zn{q$e&i!TFbEaq9tgmiZ&mys{I+kUI2QCTYa7ChJ6E=9t3pvoyn+h9dkK+2wmymR? aSdpHPKiI!KgO$t2yR^>LgG3)eOaB8*H)bdR From 5a7ab777d6f8d26c3afec3334305f3e82ce4b9ff Mon Sep 17 00:00:00 2001 From: Fini Jastrow Date: Mon, 23 Oct 2023 13:38:10 +0200 Subject: [PATCH 7/7] Fixup: neovim: Improve filename [why] If the svg file is renamed the icon list has to be updated :rolleyes: Signed-off-by: Fini Jastrow --- src/svgs/icons.tsv | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/svgs/icons.tsv b/src/svgs/icons.tsv index 9632c4dc83..ff979a92cd 100644 --- a/src/svgs/icons.tsv +++ b/src/svgs/icons.tsv @@ -211,4 +211,4 @@ 177 i_custom_asm asm_nf.svg 178 i_custom_v_lang vlang_nf.svg 179 i_custom_folder_oct folder2_nf.svg -180 i_custom_neovim neovim.svg +180 i_custom_neovim neovim_nf.svg