From: bob <bobf32-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Pipe character causes pandoc to hang
Date: Fri, 2 Jun 2023 09:20:25 -0700 (PDT) [thread overview]
Message-ID: <b4c5e2db-976f-4514-8060-63b79d31ecffn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 779 bytes --]
Hi,
I have an org file which I am trying to convert to markdown. It is having
trouble with lines in the file that consist of a single pipe (|) character
only. Such files cause pandoc to hang during the conversion, with the
memory usage steadily increasing.
Anyone know of a way I can get this type of conversion to succeed, without
changing the file contents?
--
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/b4c5e2db-976f-4514-8060-63b79d31ecffn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1114 bytes --]
next reply other threads:[~2023-06-02 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 16:20 bob [this message]
[not found] ` <b4c5e2db-976f-4514-8060-63b79d31ecffn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-02 18:39 ` John MacFarlane
[not found] ` <6DD9491F-5D27-4AF2-A0F6-7AAD22499858-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-02 22:05 ` bob
[not found] ` <15df8571-93a3-461b-b7bd-5490cfeb5371n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-06-02 22:20 ` John MacFarlane
[not found] ` <7636998A-CDCA-4DCA-AFD7-AE1A0A501227-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-06-03 5:34 ` Bastien DUMONT
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=b4c5e2db-976f-4514-8060-63b79d31ecffn@googlegroups.com \
--to=bobf32-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).