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: Understanding new style writer
Date: Tue, 15 Feb 2022 15:23:56 -0800 [thread overview]
Message-ID: <yh480k4k4zhfxv.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <87wnhvg9zo.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org> writes:
> Hi Günter,
>
> Günter Dannoritzer <dannoritzer-S0/GAf8tV78@public.gmane.org> writes:
>
>> in the pandoc manual it shows under custom-writers how to create a
>> writer.
>
> This feature has not been released yet, and should probably not be
> mentioned on the website. You can already test it by using one of the
My mistake; I will revert it to the documentation for the released version!
--
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/yh480k4k4zhfxv.fsf%40johnmacfarlane.net.
prev parent reply other threads:[~2022-02-15 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 19:06 Günter Dannoritzer
[not found] ` <12d035a5-f3c1-475a-9ae5-db014361514an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-02-15 19:44 ` Albert Krewinkel
[not found] ` <87wnhvg9zo.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-02-15 22:09 ` Günter Dannoritzer
[not found] ` <868a108d-f233-4f5c-bfe7-f26dc8bafffan-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-02-17 7:44 ` Albert Krewinkel
[not found] ` <87bkz6exuy.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-02-18 20:58 ` Günter Dannoritzer
2022-02-15 23:23 ` John MacFarlane [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=yh480k4k4zhfxv.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).