public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: pandoc lua vs. pandoc
Date: Mon, 27 Mar 2023 16:56:29 +0200	[thread overview]
Message-ID: <87bkkez1b7.fsf@zeitkraut.de> (raw)
In-Reply-To: <CADAJKhDOC98BQ4UY+oKTMa4mfSgJMX8+J0GfXk=q3ebL-dFYYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Is there any global value which is guaranteed to have different
> values when running as `pandoc lua` vs. running as `pandoc`? 
>
> My use case is a script which should work both as a filter and as a
> standalone script and print some info in the latter case.
>
> It seems like `PANDOC_STATE` is nil when running as `pandoc lua`, but
> is this always so, and/or is there a better option?

The `PANDOC_STATE` variable being nil might be a bug, I'll have to check
that. The `arg` global should be a good indicator: it will always be set
to a table value when running `pandoc lua`, but never in filters or
custom readers/writers.


-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124

-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/87bkkez1b7.fsf%40zeitkraut.de.


      parent reply	other threads:[~2023-03-27 14:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 14:11 BPJ
     [not found] ` <CADAJKhDOC98BQ4UY+oKTMa4mfSgJMX8+J0GfXk=q3ebL-dFYYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-03-27 14:56   ` Albert Krewinkel [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

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

  git send-email \
    --in-reply-to=87bkkez1b7.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).