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: Re: “PANIC” error message with custom writer
Date: Sun, 18 Jan 2015 18:39:28 -0800 (PST)	[thread overview]
Message-ID: <37f4d724-11e4-4104-abba-8388b88f1eaf@googlegroups.com> (raw)
In-Reply-To: <20141222163759.GD95411-bi+AKbBUZKaOwiQRAsGx7a+gxsCIUpAnHiGdP5j34PU@public.gmane.org>


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

After extensive deletions resulting in a ‘writer’ that contained nothing 
but the utility function which tells you which functions are missing at run 
time, I have determined that my code was in fact flawless; the problem was 
that, in my enthusiasm for doing a thing properly, I had added a shebang 
(#!) line to the beginning of the script, without really thinking about it.

Since Lua supposedly treats every file as an independent “chunk” (to use 
the official term), I don’t understand why this should cause trouble, but 
if anyone else runs into a similar issue, at least now we know the fix is 
easy.

In the course of my investigations, I also discovered that Pandoc’s 
internal Lua engine is two revisions out of date. I know Lua 5.3 was only 
released last week, but it includes very basic UTF-8 support, so I was 
really looking forward to using it. Given that even 5.2 was never 
incorporated into Pandoc, I am not very optimistic about that.

-- 
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/37f4d724-11e4-4104-abba-8388b88f1eaf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

  parent reply	other threads:[~2015-01-19  2:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-20 21:07 Gordon Steemson
     [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 [this message]
     [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=37f4d724-11e4-4104-abba-8388b88f1eaf@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).