From: Water Lin <WaterLin@ymail.com>
To: Mikael Fornius <firstname.lastname@example.org>
Cc: email@example.com, Carsten Dominik <firstname.lastname@example.org>
Subject: Re: The Perl color style
Date: Tue, 13 Oct 2009 17:37:37 +0800 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Mikael Fornius's message of "Tue, 13 Oct 2009 11:26:14 +0200")
Mikael Fornius <email@example.com> writes:
> Water Lin <WaterLin@ymail.com> writes:
>>>> , Emacs will tell me the error:
>>>> face-attribute: Invalid face: quote
>>>> Could not find config file "~/.tidyrc". Winging it.
> This looks as a configuration typo or similar problem.
> Maybe you should try to enalble emacs "debug on error" feature:
> M-x toggle-debug-on-error RET
> , retry the org-export command and see if any information on why you
> have errors show up in the backtrace.
> If you have problem reading the backtrace you can post it here and I
> will give it a try.
>> I am sorry. I don't think I catch your idea. I have my own htmlize.el
>> whoes version is 1.36. But I don't know whether Org is using this one.
>> How can I find out this?
> M-: htmlize-version RET
> can give an answer when htmlize-package is loaded.
I think I found the reason, there is something wrong with my Perl
script, so htmlize can't parse it and add color.
I changed a different script and tried htmlize, the Perl color is good.
Water Lin's notes and pencils: http://en.waterlin.org
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
prev parent reply other threads:[~2009-10-13 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 8:27 The Perl color style Water Lin
2009-10-12 8:58 ` Mikael Fornius
2009-10-12 9:19 ` Water Lin
2009-10-12 13:33 ` Carsten Dominik
2009-10-13 8:51 ` Water Lin
2009-10-13 9:26 ` Mikael Fornius
2009-10-13 9:37 ` Water Lin [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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).