git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [RFC/PATCH] gitweb: Syntax highlighting support
Date: Thu, 18 Feb 2010 14:01:12 -0800 (PST)	[thread overview]
Message-ID: <m3sk8ymcga.fsf@localhost.localdomain> (raw)
In-Reply-To: <20100217212855.2014.49834.stgit@localhost.localdomain>

Jakub Narebski <jnareb@gmail.com> writes:

> From: Johannes Schindelin <johannes.schindelin@gmx.de>
> 
> It requires the 'highlight' program to do all the heavy-lifting:
> http://www.andre-simon.de / http://wiki.andre-simon.de

[...]
> ---
> This is a RFC, because there exist other syntax highlighters that can
> function as filter (take input from STDIN, and write result to STDOUT),
> and have (X)HTML among supported output formats.  Beside 'highlight'
> by Andre Simon, there is also 'source-highlight' (GNU Source Highlight),
> and probably other programs.  

Actually GNU Source Highlight (http://www.gnu.org/software/src-highlite)
as it is now wouldn't be a good fit for gitweb, because it lacks 
equivalent of Highlight '--fragment' option; even with '--no-doc' it
prefixes contents with some comments and wraps the whole with <pre><tt>
tags.

On the other hand side one can also use Perl modules from CPAN for
syntax highlighting.  It would be nice to have this option for syntax
highlighting in gitweb.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

      parent reply	other threads:[~2010-02-18 22:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 21:43 [RFC/PATCH] gitweb: Syntax highlighting support Jakub Narebski
2010-02-18 10:04 ` Johannes Schindelin
2010-02-18 19:00   ` Jakub Narebski
2010-02-18 22:01 ` Jakub Narebski [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=m3sk8ymcga.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    /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).