I have multiple machines, and I was able to trace the bug to homebrew's recipe for installing Asciidoctor.

Homebrew calls the gem command associated with the system Ruby, even if a more modern Ruby is earlier on the PATH. This then requires that one uses the full path to that gem command for Asciidoctor maintenance, such as adding Pygment support.

Clearly, one shouldn't use homebrew; just use gem, as the Asciidoctor documentation specifies.

---

If you reply to this email, your message will be added to the discussion below:

http://discuss.asciidoctor.org/Pygments-fails-because-Asciidoctor-uses-system-gem-despite-brew-tp6783p6792.html

To start a new topic under Asciidoctor :: Discussion, email [hidden email]
To unsubscribe from Asciidoctor :: Discussion, click here.
NAML