List for cgit developers and users
 help / color / mirror / Atom feed
From: mailings at hupie.com (Ferry Huberts)
Subject: [PATCH v3 RESEND 1/2] highlight: fix commandline options for different highlight versions
Date: Sun, 18 Mar 2012 12:33:28 +0100	[thread overview]
Message-ID: <4F65C808.7050709@hupie.com> (raw)
In-Reply-To: <20120318113036.GH15839@hjemli.net>

while you're at it, just realized that it's not CentOS 5/6 but EPEL 
5/6... :-)

On 18-03-12 12:30, larsh at hjemli.net wrote:
> 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

-- 
Ferry Huberts





      reply	other threads:[~2012-03-18 11:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-18 10:44 mailings
2012-03-18 10:44 ` [PATCH v3 RESEND 2/2] highlight: add a workaround for the --force bug mailings
2012-03-18 11:14 ` [PATCH v3 RESEND 1/2] highlight: fix commandline options for different highlight versions larsh
2012-03-18 11:19   ` mailings
2012-03-18 11:30     ` larsh
2012-03-18 11:33       ` mailings [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F65C808.7050709@hupie.com \
    --to=cgit@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).