From: Volkan YAZICI <volkan.yazici@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: htmlize.sh
Date: Fri, 27 Mar 2009 23:49:42 -0700 (PDT) [thread overview]
Message-ID: <1e593458-40cf-4249-bddf-7b9266cfbf47@w34g2000yqm.googlegroups.com> (raw)
In-Reply-To: 20090327233056.3d90939f@halmanfloyd.lan.local
On Mar 28, 12:30 am, Marek Kubica <ma...@xivilization.net> wrote:
> Well, you probably could've used Pygments. It has a (LaTeX) interface
> called Texments, maybe that would help you?
(I didn't know about Texments, I'll check that.) I tried Pygments too,
but I also needed to hack the sources to be able to introduce CLHS,
MOP, etc. linking stuff. I found it easier to hack some elisp file on-
the-fly via emacs, than hacking a piece of python code that I'm not
familiar with.
> It supports Common Lisp, Scheme (to some extent, some things are
> missing yet) and Clojure.
I like the *completeness* of emacs in such scenarios. (On the other
hand, if I'm not mistaken, emacs supports much more languages than any
other syntax highlighting tools in the wild.)
Regards.
next prev parent reply other threads:[~2009-03-28 6:49 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 ` htmlize.sh Marek Kubica
2009-03-28 6:49 ` Volkan YAZICI [this message]
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=1e593458-40cf-4249-bddf-7b9266cfbf47@w34g2000yqm.googlegroups.com \
--to=volkan.yazici@gmail.com \
--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).