From: BP Jonsson <bpjonsson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: CodeBlock elements in pandocfilters.py stringify function
Date: Sun, 3 Nov 2013 17:20:20 +0100 [thread overview]
Message-ID: <CAFC_yuSz_Egh8wE_D2Eu+6uFrFYZLHJ34QAh0_NDLM3UidxSbg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
John, I see that CodeBlock elements are ignored by the stringify function
in pandocfilters.py. Is there any particular reason for that?
Also wouldn't it be a good idea to insert spaces after block elements?
I'm writing my perl version and wonder if since elements are represented by
objects anyway and stringify will likely be an object method would
potential users find it a good idea if string representation of objects
were overloaded to call that method?
--
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/CAFC_yuSz_Egh8wE_D2Eu%2B6uFrFYZLHJ34QAh0_NDLM3UidxSbg%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
[-- Attachment #2: Type: text/html, Size: 1368 bytes --]
next reply other threads:[~2013-11-03 16:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 16:20 BP Jonsson [this message]
[not found] ` <CAFC_yuSz_Egh8wE_D2Eu+6uFrFYZLHJ34QAh0_NDLM3UidxSbg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-04 16:15 ` John MacFarlane
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=CAFC_yuSz_Egh8wE_D2Eu+6uFrFYZLHJ34QAh0_NDLM3UidxSbg@mail.gmail.com \
--to=bpjonsson-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).