From: "Björn Peemöller" <bjp-jNDFPZUTrfRKC+uPiMyuuyYxWCU7E+c1@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Problem at parsing code block with long attributes
Date: Tue, 11 Jun 2013 14:53:30 +0200 [thread overview]
Message-ID: <51B71DCA.2060105@informatik.uni-kiel.de> (raw)
Hi,
I just discovered a strange behaviour when it comes to fenced code
blocks with long attributes. When I process the following file
~~~~~~
Text.
~~~ {.java .numberLines include="3_ExtendedBuffer/TimeException.java"}
foo
~~~
Text.
~~~ {.java .numberLines include="3_ExtendedBuffer/TimeonException.java"}
bar
~~~
~~~~~~
using `cat test.markdown | pandoc -t markdown`, I get
~~~~~~
Text.
~~~~ {.java .numberLines include="3_ExtendedBuffer/TimeException.java"}
foo
~~~~
Text.
~~~~
{.java .numberLines include="3_ExtendedBuffer/TimeonException.java"}
bar
~~~~
~~~~~~
That is, in the second code block the attributes are parsed as content
of the code block.
Can somebody explain this behaviour? I'm using pandoc 1.11.1.
Thanks in advance,
Björn
--
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/51B71DCA.2060105%40informatik.uni-kiel.de?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.
next reply other threads:[~2013-06-11 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 12:53 Björn Peemöller [this message]
[not found] ` <51B71DCA.2060105-jNDFPZUTrfRKC+uPiMyuuyYxWCU7E+c1@public.gmane.org>
2013-06-11 13:08 ` Joost Kremers
[not found] ` <m2obbcpzgu.fsf-4Qa7NeS2ENVPDCrvnpRrPfNq91seawkrvu54Y+ZNwJg@public.gmane.org>
2013-06-11 17:17 ` 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=51B71DCA.2060105@informatik.uni-kiel.de \
--to=bjp-jndfpzutrfrkc+upimyuuyyxwcu7e+c1@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).