From mboxrd@z Thu Jan  1 00:00:00 1970
From: larsh at hjemli.net (larsh at hjemli.net)
Date: Sun, 18 Mar 2012 11:30:36 +0000
Subject: [PATCH v3 RESEND 1/2] highlight: fix commandline options for
 different highlight versions
In-Reply-To: <4F65C4C6.7090002@hupie.com>
References: <1332067457-15050-1-git-send-email-mailings@hupie.com>
 <20120318111410.GF15839@hjemli.net> <4F65C4C6.7090002@hupie.com>
Message-ID: <20120318113036.GH15839@hjemli.net>

On Sun, Mar 18, 2012 at 12:19:34PM +0100, Ferry Huberts wrote:
> 
> 
> On 18-03-12 12:14, larsh at hjemli.net wrote:
> >I really don't want the filter scripts to perform any more work than
> >necessary, so maybe we could to something like this instead:
> >
> >diff --git a/filters/syntax-highlighting.sh 
> >b/filters/syntax-highlighting.sh
> >index 6283ce9..183bd68 100755
> >--- a/filters/syntax-highlighting.sh
> >+++ b/filters/syntax-highlighting.sh
> >@@ -42,4 +42,8 @@ EXTENSION="${BASENAME##*.}"
> >  # map Makefile and Makefile.* to .mk
> >  [ "${BASENAME%%.*}" == "Makefile" ]&&  EXTENSION=mk
> >
> >+# This is for highlight v2
> >  exec highlight --force -f -I -X -S $EXTENSION 2>/dev/null
> >+
> >+# If you're using highlight v3, use this command instead:
> >+#exec highlight --force -f -I -O xhtml -S $EXTENSION 2>/dev/null
> >--
> >larsh
> 
> fine with me. I just thought making it automatic was the way to go. this 
> is perfectly ok with me.
> can you retain the comment though?

Certainly, and I'll do something similar with the --force bug in patch 2/2.

--
larsh