public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: iandol <iandol-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Learning how Lua filters work through Debugging?
Date: Wed, 26 Jun 2019 19:49:12 -0700 (PDT)	[thread overview]
Message-ID: <620bb703-64b0-43e3-b4b5-0c0ce34181e0@googlegroups.com> (raw)
In-Reply-To: <871rzgywgd.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>


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

On Thursday, 27 June 2019 03:32:13 UTC+8, Albert Krewinkel wrote:
>
>
> This would be great. I never tried ZeroBrane, but reading about its 
> debugging feature makes me believe that debugging should be possible. 
> One problem might be that pandoc is not (yet) available as a Lua module: 
> you would have to setup pandoc as the Lua interpreter in ZeroBrane, and 
> I don't know how easy that is. 
>

 Thanks Albert! I tried ZeroBrane, using environment variables to access 
mobdebug and socket files to the path before running, and putting `
*require("mobdebug").start()*` in the script. Running pandoc normally from 
the commandline did trigger the Zerobrane Debug server, however although A 
could put a breakpoint in the main top-level code, I couldn't put a 
breakpoint within a function call nor step into the function from outside 
it (e.g. *function Emph(elem)*). I assumed Lua is V5.3 in Pandoc, is that 
correct? As I understand it, the remote debugger does not need to know 
Pandoc is hosting Lua, as the debugger communicates via a socket to the 
process. ZeroBrane is really nice, extremely fast and great documentation! 
So TLDR; is that the remote debugger does trigger without needing to 
specify Pandoc, but there was an issue with stepping into functions. 
ZeroBrane is close to being an ideal solution...

I also tried using Visual Studio Code and an extension that supports remote 
debug: https://github.com/actboy168/lua-debug — but instructions are in 
Chinese and I didn't have enough time to get it to work…

Thanks for the links to learning materials.

-- 
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/620bb703-64b0-43e3-b4b5-0c0ce34181e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

  parent reply	other threads:[~2019-06-27  2:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-26 11:29 iandol
     [not found] ` <cffd9ff2-b19b-45e0-8529-43ddfa26582d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-06-26 19:32   ` Albert Krewinkel
     [not found]     ` <871rzgywgd.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2019-06-27  2:49       ` iandol [this message]
     [not found]         ` <620bb703-64b0-43e3-b4b5-0c0ce34181e0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-28  3:04           ` iandol
     [not found]             ` <5c926b63-e3fc-4fd5-ab4a-77b3bafc5273n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-28  5:29               ` Albert Krewinkel
     [not found]                 ` <87pn66jwol.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-09-28 11:13                   ` iandol
     [not found]                     ` <c327601e-964d-48b3-a00f-edc417a2911bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-28 21:54                       ` John MacFarlane
     [not found]                         ` <m2eeml1sap.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-10-12  9:10                           ` iandol

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=620bb703-64b0-43e3-b4b5-0c0ce34181e0@googlegroups.com \
    --to=iandol-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).