-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/05/11 16:02, bulletmark wrote: > I was running pygmentize to my terminal and after your comment I have > realized that some of the output is underlined so I guess that means > pygmentize believes it is invalid syntax?
Yep, this is how the default style shows Pygments "Error" tokens. > Either way, why does sphinx just fail to render the output at all if the > highlighter trips over some syntax? Is there any message where a user can > see the reason why his code is not highlighting? It's because then you can keep the default highlight language even if you have a shell/text/whatever sample inbetween. > I spent ages on this problem thinking I had an environment problem. The > code section is not even being line numbered at all. More particularly, can > a user tell sphinx to ignore syntax errors and render (as best it can) > anyway? I imagine there will always be different language dialects which a > general purpose highlighter will not completely accommodate. Yep, we're planning an option to customize this in 1.1. Georg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAk6MbXgACgkQN9GcIYhpnLCwswCeNecHcgiZiBPKj5lcp35AKhUJ FcAAoJwLXB2+t7L6ghsVtB5Wx6+g93lK =Z0cv -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-dev@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
