emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [bug] "Invalid face" when exporting code block to HTML
Date: Fri, 06 Jan 2012 14:28:47 +0100	[thread overview]
Message-ID: <80k455j6y8.fsf@somewhere.org> (raw)
In-Reply-To: 16127.1325805522@alphaville.americas.hpqcorp.net

Hi Nick,

Nick Dokos wrote:
> Sebastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> wrote:
>> Quite "simple": the following block generates an "Invalid face" error when
>> exported to HTML.
>>
>> #+begin_src sh
>> svn checkout http://svn/trunk/dev/ mydev
>> #+end_src
>>
>> This worked yesterday. Does it ring a bell to someone? Could some recent
>> commit be responsible of this?
>
> Can't reproduce it either with a slightly earlier version of org (.19)
> or latest (.44 - note that I'm ahead of origin/master by 3 commits).
>
> Try evaluating this expression which is the one that gave you the error:
>
> (htmlize-face-size 'default)
>
> I get 113 in my setup, so this looks like an htmlize error.

Indeed:

#+begin_src emacs-lisp
Debugger entered--Lisp error: (void-function htmlize-face-size)
  (htmlize-face-size (quote default))
  eval((htmlize-face-size (quote default)) nil)
  eval-last-sexp-1(nil)
  eval-last-sexp(nil)
  call-interactively(eval-last-sexp nil nil)
#+end_src

> I don't understand where the nil face (which is indeed invalid) comes from.
>
> Also htmlize-face-size wraps the face-attribute call inside an
> (ignore-errors ...)  form, so it should *not* blow up.

I don't understand, as I did not do any Emacs changes lately in that area.

> Are you using some old outdated htmlize code by any chance?

Library is file `~/Downloads/emacs/site-lisp/htmlize.el', where I have all
independent package files downloaded from the Web.

Wait... That should be `~/src/org-mode/contrib/lisp/htmlize.el', right?
                              ^^^^^^^^^^^^^^^^
So, I have 2 `htmlize' files, and the Org-compliant one is only located in the
second best place.

I have -- still! -- absolutely no idea why the original `htmlize' file worked
for me so far, and why it suddenly stopped working yesterday (I did no change
of load-paths, neither did I save that file there... it must be a very old
reminiscence).

I still have found out that -- with the original (non-Org) `htmlize' file --,
I need to have a declaration like this:

#+begin_src emacs-lisp
       (default ((t (nil))))
#+end_src

in my color theme.

With the Org flavor of `htmlize', that line is not needed.

For sure, yesterday, I played with that line, *after* things had gone wrong,
as I wondered whether such a line, with `nil', was good or not to have.

Now, there are 2 ways to solve my problem for sure:

- putting the original `htmlize' after the Org paths,
- removing it.

The first solution does not feel natural to me: I need having the proper
load-paths set up for Org in my stub .emacs (calling my tangled, huge file
full of Emacs customizations). It's because ~/Downloads/emacs/site-lisp/ is
added to the load-path in that huge .emacs file that it's finally in front of
Org git directories, as the append is done upfront -- no prepend.

Now, I really don't need to have conflicting versions of `htmlize', so I
simply deleted that file -- whose I ignored the existence up to now --, and
all is so far so good.

Thanks (a lot) for putting me right on track!

Best regards,
  Seb

-- 
Sebastien Vauban

      reply	other threads:[~2012-01-06 13:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 22:06 [bug] "Invalid face" when exporting code block to HTML Sebastien Vauban
2012-01-05 23:18 ` Nick Dokos
2012-01-06 13:28   ` Sebastien Vauban [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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=80k455j6y8.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).