public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: bob <bobf32-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pipe character causes pandoc to hang
Date: Fri, 2 Jun 2023 15:05:36 -0700 (PDT)	[thread overview]
Message-ID: <15df8571-93a3-461b-b7bd-5490cfeb5371n@googlegroups.com> (raw)
In-Reply-To: <6DD9491F-5D27-4AF2-A0F6-7AAD22499858-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1941 bytes --]

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 <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 pandoc-discus...-/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
> .
>
>

-- 
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/15df8571-93a3-461b-b7bd-5490cfeb5371n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2961 bytes --]

  parent reply	other threads:[~2023-06-02 22:05 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 [this message]
     [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=15df8571-93a3-461b-b7bd-5490cfeb5371n@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).