unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marek Kubica <marek@xivilization.net>
To: help-gnu-emacs@gnu.org
Subject: Re: htmlize.sh
Date: Fri, 27 Mar 2009 23:30:56 +0100	[thread overview]
Message-ID: <20090327233056.3d90939f@halmanfloyd.lan.local> (raw)
In-Reply-To: 018d3c1a-bf21-49f2-bc78-75562c7a36f6@e38g2000yqa.googlegroups.com

On Fri, 27 Mar 2009 13:25:10 -0700 (PDT)
Volkan YAZICI <volkan.yazici@gmail.com> wrote:

> Hi,
> 
> I've been looking for a syntax highlighter to integrate into texinfo
> to be able to colorize @lisp ... @end blocks. Actually, not just a
> syntax highlighting tool, I also want to be able to supply links to
> certain commands. (E.g. CLHS and MOP links to related Common Lisp
> commands.) Below are some of my experiences during my research.
> 
> - I first tried my luck with Syntax::Highlight::Engine::Kate module.
> (Hey, texi2html is also written in Perl, should be easy to integrate.)
> But it doesn't take long to figure out that it is quite broken for
> Lisp family of programming languages.
> 
> - You know that flashy http://paste.lisp.org/ pastebin, and it's code
> is a F/OSS. Despite it took a half of a day to decouple lisppaste from
> its unnecessary dependencies (e.g. araneida web server!), at the end
> I'm disappointed by the fact that I need to implement my own parsing
> routines for every other programming language.

Well, you probably could've used Pygments. It has a (LaTeX) interface
called Texments, maybe that would help you?
It supports Common Lisp, Scheme (to some extent, some things are
missing yet) and Clojure.

regards,
Marek


  reply	other threads:[~2009-03-27 22:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 20:25 htmlize.sh Volkan YAZICI
2009-03-27 22:30 ` Marek Kubica [this message]
2009-03-28  6:49   ` htmlize.sh Volkan YAZICI
2009-04-04 21:32 ` htmlize.sh Thien-Thi Nguyen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=20090327233056.3d90939f@halmanfloyd.lan.local \
    --to=marek@xivilization.net \
    --cc=help-gnu-emacs@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).