Feel free to open a PR!

Depending on the program, options can be in any order. Here for example both are valid commands.

@Anhsirkz how did you install figlet? If there's a different implementation we could try to make the examples work on both.

@acuteenvy
nix-shell -p figlet
Using the latest 24.11 channel.

Both commands work for me when using figlet from nixpkgs. What's the error you're getting?

The argument I would make is consistency. While both are valid commands, we tend to put options before positional arguments in examples.

@acuteenvy I don't know how this is possible:
figlet thin -f thin outputs thin -fthin stylized in the default font.
figlet -f thin thin outputs thin stylized with the thin font.

@Managor Wouldn't your statement be a contradiction to my findings?

I feel like you have a different implementation

What does figlet -v return for you?

FIGlet Copyright (C) 1991-2012 Glenn Chappell, Ian Chai, John Cowan,
Christiaan Keet and Claudio Matsuoka
Internet: <info@figlet.org> Version: 2.2.5, date: 31 May 2012

FIGlet, along with the various FIGlet fonts and documentation, may be
freely copied and distributed.

If you use FIGlet, please send an e-mail message to <info@figlet.org>.

The latest version of FIGlet is available from the web site,
        http://www.figlet.org/

Usage: figlet [ -cklnoprstvxDELNRSWX ] [ -d fontdirectory ]
              [ -f fontfile ] [ -m smushmode ] [ -w outputwidth ]
              [ -C controlfile ] [ -I infocode ] [ message ]

figlet -v returns the same output according to diff

Very curious. Shame we were not able to find the root cause. Since the common command that works for both of us is figlet -f font text, I see no reason to not change the example. Would you be willing to fire up a pull request or shall I do it?

Please go ahead and do the PR. 👍