As a Docco user, I want to be able to produce non-highlighted documentation when Pygments is not available, rather than failing to produce any output whatsoever, and exiting the process with a failure code.
When the Pygments output is not present, output escaped codeText for each section.
There are no direct unit tests for this functionality, but it is directly tested by my continuous integration build, on my fork of Docco, which does not have pygments available during the build tests.
This pull request has the side-effect of enabling, but does not include support for, continuous integration testing of Docco via travis-ci.
Add support for using plaintext code output when pygments is not pres…
…ent, rather than failing entirely.
Update docs/docco lib
Nice, but I don't think we need an error. If it's a feature that it can produce plaintext docs, let's just allow it to produce 'em ... and if you install pygments, they'll get highlights.
Do not produce an error when Pygments is not present, just output pla…
…intext code blocks.
Good call, done and done.
I had to no-op the error handlers, rather than remove them, so that node doesn't throw an error when pygments is missing.
Note that Travis-CI reports this as breaking the build, because I don't have a checked in .travis.yml for this branch.
The master branch includes these changes and is currently :