From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pipe character causes pandoc to hang
Date: Sat, 3 Jun 2023 05:34:17 +0000 [thread overview]
Message-ID: <ZHrQ2Tznw1uRB6qD@localhost> (raw)
In-Reply-To: <7636998A-CDCA-4DCA-AFD7-AE1A0A501227-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
These lines are interpreted as empty tables. The org-mode manual suggests you add a zero-width space before the pipe character in such cases: https://orgmode.org/org.html#Escape-Character
Le Friday 02 June 2023 à 03:20:20PM, John MacFarlane a écrit :
> I’m not sure…Albert Krewinkel would know. If nobody replies, open an issue.
>
>
> On Jun 2, 2023, at 3:05 PM, bob <bobf32-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Thank you. I was not using the latest pandoc version. Having upgraded I
> tried the conversion again and this time a conversion was carried out, but
> now all lines that consist of a single pipe character are completely
> removed from the resulting markdown file.
>
> Is this expected behaviour?
>
> On Friday, June 2, 2023 at 7:40:02 PM UTC+1 John MacFarlane wrote:
>
> Sounds like a bug in the org reader, which should be reported on our
> issue tracker, if you can give a short reproducible example. (Also make
> sure you've tested it with the latest pandoc.)
>
> > On Jun 2, 2023, at 9:20 AM, bob <[1]bob...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >
> > 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 [2]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit [3]https://groups.google.com
> /d/msgid/pandoc-discuss/
> b4c5e2db-976f-4514-8060-63b79d31ecffn%40googlegroups.com.
>
>
>
> --
> 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 [4]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit [5]https://groups.google.com/d/
> msgid/pandoc-discuss/
> 15df8571-93a3-461b-b7bd-5490cfeb5371n%40googlegroups.com.
>
>
> --
> 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 [6]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit [7]https://groups.google.com/d/msgid/
> pandoc-discuss/7636998A-CDCA-4DCA-AFD7-AE1A0A501227%40gmail.com.
>
> References:
>
> [1] -
> [2] -
> [3] https://groups.google.com/d/msgid/pandoc-discuss/b4c5e2db-976f-4514-8060-63b79d31ecffn%40googlegroups.com
> [4] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [5] https://groups.google.com/d/msgid/pandoc-discuss/15df8571-93a3-461b-b7bd-5490cfeb5371n%40googlegroups.com?utm_medium=email&utm_source=footer
> [6] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [7] https://groups.google.com/d/msgid/pandoc-discuss/7636998A-CDCA-4DCA-AFD7-AE1A0A501227%40gmail.com?utm_medium=email&utm_source=footer
--
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/ZHrQ2Tznw1uRB6qD%40localhost.
prev parent reply other threads:[~2023-06-03 5:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 16:20 bob
[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 [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=ZHrQ2Tznw1uRB6qD@localhost \
--to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).