Skip to content

Commit fef67f3

Browse files
committed
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]>
1 parent aabed73 commit fef67f3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

readme.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -344,7 +344,7 @@ Patching the font of your own choosing for use with the [VimDevIcons ➶][vim-de
344344
* Alternative usage: Execute the patcher with the FontForge binary using the script flag:
345345

346346
```
347-
./fontforge -script font-patcher PATH_TO_FONT
347+
fontforge -script font-patcher PATH_TO_FONT
348348
```
349349

350350
* Patching fonts using the AppImage:

0 commit comments

Comments
 (0)