public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Gordon Steemson <gsteemso-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: “PANIC” error message with custom writer
Date: Sat, 20 Dec 2014 13:07:33 -0800 (PST)	[thread overview]
Message-ID: <fc67fe32-8b42-4ba3-9ef5-a072a47fd8d9@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2369 bytes --]

Hi all,

I am using Pandoc (by way of a Perl script called from within TextWrangler 
on Mac OS 10.6.8) to publish my amateurish scribblings to a variety of fan 
fiction repositories on the Web. All of them bar my own personal site use 
an extremely crippled subset of HTML with no stylesheet support as an input 
format, and just to make things extra fun, the nature of the HTML crippling 
varies from repository to repository. This is easily gotten around in 
theory by making a custom writer for each repository, but the first one I 
tried (for fanfiction.net) is giving me serious and intractable problems.

First was the fact that nowhere is it apparently documented what directory 
the “-t path/to/custom_writer.lua” is relative to (it definitely isn’t the 
same directory the “templates” folder lives in), and using “~” as an 
abbreviation for my home directory is apparently not supported. I finally 
got around that one by specifying an absolute path from the root of my 
filesystem, which seems unnecessarily fragile and inflexible.

Second, when I FINALLY got the damn thing to actually try to call the 
custom writer, it immediately bombed out with the following error message:

>
> PANIC: unprotected error in call to Lua API (attempt to call a string 
value)
>

This is… less than informative. Does anyone have any idea what’s going on 
here? I went over my modifications to the sample.lua file and I can’t find 
anything very different from what was supplied initially—my changes were 
almost all cosmetic, of the “turn an insertion of unsupported HTML tag X 
into an insertion of <p> (or <b>, or whatever)” variety. In the absence of 
more helpful diagnostic messages, I am completely at a loss for how to 
proceed.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/fc67fe32-8b42-4ba3-9ef5-a072a47fd8d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 2891 bytes --]

             reply	other threads:[~2014-12-20 21:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-20 21:07 Gordon Steemson [this message]
     [not found] ` <fc67fe32-8b42-4ba3-9ef5-a072a47fd8d9-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-20 21:56   ` Gordon Steemson
     [not found]     ` <8b9ae12c-20fe-4381-bf71-1394e301f902-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-21  7:32       ` Gordon Steemson
     [not found]         ` <5ea323ef-4f59-48ef-9280-9514543453b5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-22 16:37           ` John MacFarlane
     [not found]             ` <20141222163759.GD95411-bi+AKbBUZKaOwiQRAsGx7a+gxsCIUpAnHiGdP5j34PU@public.gmane.org>
2015-01-19  2:39               ` Gordon Steemson
     [not found]                 ` <37f4d724-11e4-4104-abba-8388b88f1eaf-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-19  5:40                   ` John MacFarlane
     [not found]                     ` <20150119054005.GA5491-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2015-01-19  5:50                       ` John MacFarlane
2014-12-22 16:35   ` John MacFarlane

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

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

  git send-email \
    --in-reply-to=fc67fe32-8b42-4ba3-9ef5-a072a47fd8d9@googlegroups.com \
    --to=gsteemso-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@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.
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 NNTP newsgroup(s).