From: smithj4 at bnl.gov (Jason A. Smith)
Subject: Syntax highlighting broken.
Date: Mon, 12 Aug 2013 15:29:31 -0400 [thread overview]
Message-ID: <5209379B.2050305@bnl.gov> (raw)
In-Reply-To: <52093620.9000605@hupie.com>
I understand the desire to move to a newer and possibly better syntax
highlighting tool like that python script, but since that requires
python version 3, it is not possible to use on a RHEL5/6 server, which
is a show-stopper for us. RHEL7 will probably have it, but we need to
use the current Enterprise OSes here and RHEL7 probably won't be out for
close to another year.
~Jason
On 08/12/2013 03:23 PM, Ferry Huberts wrote:
> We include scripting to use the highlight tool.
> IMHO we therefore should also ship the corresponding css.
> Removal is very unfortunate and makes the lives of users and packagers
> hard without a good reason. I frowned when I saw the patch but didn't
> want to comment until now.
>
> Either do none of it, or do all of it. I vote for all of it.
>
> Please resurrect the css
>
> On 12/08/13 21:07, Jason A. Donenfeld wrote:
>> This CSS was removed so that cgit could support multiple highlighting
>> engines without preferring one over another. Either include this CSS
>> along with the highlighted output in <style> tags (as in the case of
>> [1]) or add it back to the global CSS yourself.
>>
>> [1] http://git.zx2c4.com/cgit/tree/filters/syntax-highlighting.py
>> _______________________________________________
>> CGit mailing list
>> CGit at lists.zx2c4.com
>> http://lists.zx2c4.com/mailman/listinfo/cgit
>>
>
next prev parent reply other threads:[~2013-08-12 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 13:52 smithj4
2013-08-12 19:07 ` Jason
2013-08-12 19:23 ` mailings
2013-08-12 19:29 ` smithj4 [this message]
2013-08-12 19:57 ` mailings
2013-08-12 20:01 ` Jason
2013-08-13 19:32 ` Jason
2013-08-14 5:40 ` mailings
2013-08-14 10:53 ` cgit
2013-08-14 11:47 ` smithj4
2013-08-14 12:03 ` mailings
2013-08-14 12:24 ` cgit
2013-08-14 11:35 ` smithj4
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=5209379B.2050305@bnl.gov \
--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).