From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Albert Krewinkel
<albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Custom readers and writer paths
Date: Mon, 06 Jun 2022 11:38:21 -0700 [thread overview]
Message-ID: <yh480kv8tdd4de.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <874k0xpszm.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org> writes:
> I'm not sure if it's better or worse, but we could also look for the
> reader in LUA_PATH (via `require`). Using a bit of pseudo-code:
>
> if file_exists(reader_path) then
> dofile(reader_path)
> reader = Reader
> else
> reader = require (reader_path:gsub('.lua$', ''))
> end
>
> The reader library would have to `return` the Reader function instead of
> just defining it as a global.
Probably better not to change the interface in this way.
Maybe treating these like filters is the most sensible/least
surprising thing to do. Should we have readers/ and writers/
subdirectories of user data? Or custom-readers/ custom-writers/ ?
next prev parent reply other threads:[~2022-06-06 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 16:58 John MacFarlane
[not found] ` <m2h74xhgpp.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-06-06 17:41 ` Albert Krewinkel
[not found] ` <874k0xpszm.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-06-06 18:38 ` John MacFarlane [this message]
[not found] ` <yh480kv8tdd4de.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2022-06-06 19:53 ` BPJ
[not found] ` <CADAJKhDdwHuvBjTCAAwrFY6RcaZ+d_FRMnkVp3MMUtntrsBdYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-06 20:02 ` AW: " denis.maier-NSENcxR/0n0
2022-06-06 20:19 ` John MacFarlane
2022-06-06 20:41 ` Albert Krewinkel
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=yh480kv8tdd4de.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=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).