doc: Correct example patch call through fontforge [skip ci]

[why] The readme states that one should call `fontforge` with `./fortforge`. That means that no PATH is used, and will usually fail, because the user is in our repo and not in the directory where the fontforge binary resides in. And even if ... then the `font-patcher` script would be somewhere else. That makes no sense. [how] Drop the `./` prefix of the `fontforge` call. Signed-off-by: Fini Jastrow <[email protected]>
ryanoasis · Apr 27, 2022 · fef67f3 · fef67f3
1 parent aabed73
commit fef67f3
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/readme.md b/readme.md
@@ -344,7 +344,7 @@ Patching the font of your own choosing for use with the [VimDevIcons ➶][vim-de
 * Alternative usage: Execute the patcher with the FontForge binary using the script flag:
 
   ```
-  ./fontforge -script font-patcher PATH_TO_FONT
+  fontforge -script font-patcher PATH_TO_FONT
   ```
 
 * Patching fonts using the AppImage: