From: Achim Gratz <Stromeko@nexgo.de>
Subject: Re: worg-new-exporter successful publish locally
Date: Sun, 28 Apr 2013 21:12:40 +0200 [thread overview]
Message-ID: <877gjmcvvb.fsf@Rainer.invalid> (raw)
Jay Kerns writes:
> 1. I set up worg-local-init.el as you recommended and everything goes
> smoothly until here:
> | Publishing file /home/jay/git/worg/org-hacks.org using
> | Loading cc-langs...
> | Symbol's function definition is void: nil
Yes, I get that, too.
> Now, I have opened org-hacks.org (with the same emacs -Q as above but
> without batch) and it exports successfully to HTML from the
> interactive dispatcher. Do you have any idea what the problem might
Something in cc-langs that doe not work correctly in batch mode, it
fails to define or select the correct fontification function for gawk.
In any case, it doesn't happen when you don't export in batch mode and
Emacs 23 does not have that problem, interestingly enough…
> 2. If I don't do batch but instead publish interactively with M-x
> publish-worg, the org-hacks.org error doesn't appear but then near
> the end I get
> org-publish-get-base-files: Wrong type argument: stringp, (concat
> worg-base "org-contrib/bibtex/")
> I haven't had time to look deeper into this to see what's going on,
> but I thought you might like to know.
That's a bug in my code. This is used inside a backquoted list in some
places and should have a "," prepended there to be evaluated when
defining the list. I've fixed it on Worg.
> 3. I've been working on that invalid time format problem we've been having
> and I think I might have identified where the problem is. I will
> write about it in another message.
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
next prev parent reply other threads:[~2013-04-28 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 6:53 worg-new-exporter successful publish locally Jay Kerns
2013-04-27 6:59 ` Bastien
2013-04-27 8:38 ` Carsten Dominik
2013-04-27 8:40 ` Thorsten Jolitz
2013-04-27 13:33 ` Jay Kerns
2013-04-27 15:43 ` Achim Gratz
2013-04-28 16:44 ` Jay Kerns
2013-04-28 19:12 ` Achim Gratz [this message]
2013-04-28 19:43 ` Jay Kerns
2013-04-28 20:21 ` Achim Gratz
2013-04-28 21:17 ` Jay Kerns
2013-05-01 17:51 ` Achim Gratz
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).