all repos — cgit @ f50be7fda0a7ab57009169dd5905fcbab8eb5166

a hyperfast web frontend for git written in c

filters/syntax-highlighting.sh: work around highlight --force bug
Ferry Huberts ferry.huberts@pelagic.nl
Sun, 18 Mar 2012 11:48:01 +0000
commit

f50be7fda0a7ab57009169dd5905fcbab8eb5166

parent

375353caffb0a251e7f0174aa9b73cc1961e93fd

1 files changed, 17 insertions(+), 0 deletions(-)

jump to
M filters/syntax-highlighting.shfilters/syntax-highlighting.sh

@@ -42,4 +42,21 @@ # This is for version 2

exec highlight --force -f -I -X -S $EXTENSION 2>/dev/null # This is for version 3 +# +# On CentOS 6.2 (using highlight from EPEL), when highlight doesn't know about +# an EXTENSION, it outputs a lua error and _no_ text, even when the --force +# option is used. +# +# Also see the bug reports at: +# http://sourceforge.net/tracker/?func=detail&aid=3490017&group_id=215618&atid=1034391 +# https://bugzilla.redhat.com/show_bug.cgi?id=795567 +# +# This workaround can be removed when the bug is fixed upstream and the new +# version is packaged in most distributions. +# +# The workaround is to set the extension to 'txt' (plain text) when highlight +# exits with an error (doesn't know the format). +# +#echo "test" | highlight -f -I -O xhtml -S $EXTENSION &>/dev/null +#[ ${?} -ne 0 ] && EXTENSION="txt" #exec highlight --force -f -I -O xhtml -S $EXTENSION 2>/dev/null