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: Lua filters: Extensions with pandoc.read?
Date: Tue, 04 Oct 2022 15:31:02 +0200	[thread overview]
Message-ID: <87r0zn3dff.fsf@zeitkraut.de> (raw)
In-Reply-To: <CADAJKhCg3rMk+0fJBOcte32BVh2c9tYQHa57DEGHdyAz2u7+kQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


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

> Den tis 4 okt. 2022 11:52Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org> skrev:
>>    -- absolute set of extensions
>>    { format = 'docx',
>>    , extensions = {'auto_identifiers', 'styles', 'citations'}
>>    }
>
> This `extensions` field would be identical to the `enable` field,
> wouldn't it, or would it mean that all default extensions not
> explicitly mentioned in it would be disabled? And what would happen if
> someone uses it together with `disable` and/or `enable`; which would
> be ignored, or would it be an error condition?

Mmmh, good point. My initial idea was to use the format's default
extension when no `extensions` field is given. But that's confusing,
because now omitting the `extensions` field can have multiple meanings
("fall back to reader options" or "use default extensions"), depending
on which other fields are set. Not a good interface.

Maybe extensions should be Lua objects with some convenient methods:

``` lua
{ format: 'markdown',
  extensions: pandoc.extensions.default('markdown'):disable{'smart'}
}
```

Bit more typing, but much cleaner.

> If the format can be a table as described I think it is better to
> always ignore the format/extension info in the ReaderOptions — and
> say so clearly in the documentation!

Yes, I think you are right.

> Also I assume that `pandoc.write()` would behave analogously?

Definitely, `read` and `write` should stay symmetric.

-- 
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/87r0zn3dff.fsf%40zeitkraut.de.


  parent reply	other threads:[~2022-10-04 13:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 12:02 BPJ
     [not found] ` <CADAJKhCqSXXZBPvXRfr+h4ady_yCzO6s=VDKY_Tt54dcLtDR5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-09-19 12:39   ` Albert Krewinkel
     [not found]     ` <87czbrfrzr.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-09-19 13:34       ` BPJ
     [not found]         ` <CADAJKhApJjnCMghJ61rg6H2U9_zOP3Q=RJxHc9E2dFUH0Py+Sg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-10-04  9:13           ` Albert Krewinkel
     [not found]             ` <87v8oz3ohm.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-10-04 10:33               ` BPJ
     [not found]                 ` <CADAJKhCg3rMk+0fJBOcte32BVh2c9tYQHa57DEGHdyAz2u7+kQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-10-04 13:31                   ` Albert Krewinkel [this message]
     [not found]                     ` <87r0zn3dff.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-10-04 17:25                       ` John MacFarlane
     [not found]                         ` <5AC38771-6A87-47C2-80C7-5C7B389EDD1B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-06 11:11                           ` BPJ
     [not found]                             ` <CADAJKhCan6ec3ruV5r08ynTFPVLUtOpc=h+Jt7-geYNUcJb6QA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-10-07  6:16                               ` BPJ

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=87r0zn3dff.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).