On Mon, 26 Sept 2022 at 15:26, Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org> wrote:

Would splitting the inline code in two inlines be acceptable for you?
`veryLongClassNameWhichShouldBreak`\
`ALineInOutputFile`.

Le Monday 26 September 2022 à 02:44:32PM, A A a écrit :
> You can always break the line before and after the code span.
>
> I’m aware of that. My question is about how I can break the line within the
> code span.
>
> Do you really have inline code spans, let alone class names, which are
> longer than ca 70-80 characters
>
> I just happen to be using 78 characters as maximum column count in my source
> file in Vim. Different situations arise where the inline code needs to be
> broken up into multiple lines. Long file paths, inline code that occurs at the
> end of a line, long class names or commands exceeding 78 characters, you name
> it.
>
> In such a case I would express things differently so that I can use a code
> block
>
> I don’t like that reasoning at all. Long inline code can and will occur in a
> variety of use cases. Just because one can circumvent the problem by replacing
> with a code block doesn’t mean they should. Please trust that for the purposes
> of my question I really do need inline code and really do need to break it up
> at the end of a line.
>
> I would be very surprised if this wasn't supported in the current
> implementation of Pandoc's Markdown.
>
>
>
>
> On Fri, 23 Sept 2022 at 16:40, BPJ <[1]bpj-J3H7GcXPSITLoDKTGw+V6w@public.gmane.org> wrote:
>
> You can always break the line before and after the code span. Do you really
> have inline code spans, let alone class names, which are longer than ca
> 70-80 characters, or very short lines? In such a case I would express
> things differently so that I can use a code block. Or is it in a table? You
> can use code blocks in a grid table.
>
> Den fre 23 sep. 2022 15:42A A <[2]amine.aboufirass-Re5JQEeQqe8@public.gmane.orgm> skrev:
>
>
> Hello,
>
> I’d like to do the same for inline code. I’ve found that going from
>
> `veryLongClassNameWhichShouldBreakALineInOutputFile`
>
> to
>
> `veryLongClassNameWhichShoul
> dBreakALineInOutputFile`
>
> Will actually introduce a space at the linebreak in the output,
> something which I do not want.
>
> Any ideas on how to break up long lines like that without compromising
> the output?
>
> Regards,
>
> Amine
>
>
> On Fri, 23 Sept 2022 at 12:54, A A <[3]amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> wrote:
>
> It works. Thanks.
>
> On Fri, 23 Sept 2022 at 12:23, Bastien DUMONT <[4]
> bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org> wrote:
>
> Thus (but it is not so pretty):
>
> ![Data binding button default conversion](
> data-binding-button-default-conversion.png
> ){#fig:data-binding-button-default-conversion}
>
> (Beware the curly brackets for the classes and attributes.)
>
> Le Friday 23 September 2022 à 11:52:00AM, A A a écrit :
> > Hello,
> >
> > I have the following markdown:
> >
> > ![Data binding button default conversion]
> (data-binding-button-default-conversion.png)(#
> fig:data-binding-button-default-conversion)
> >
> > I’d like to break this up into multiple lines in the markdown
> source to keep
> > everything clean and organized. So I tried that:
> >
> > ![Data binding button default conversion]
> > (data-binding-button-default-conversion.png)
> > (#fig:data-binding-button-default-conversion)
> >
> > Unfortunately it looks like Pandoc doesn’t recognize the
> above as an Image in
> > the AST but rather just a string of text.
> >
> > How can I break up a long image description into multiple
> lines without
> > compromising the markdown?
> >
> > Thanks for your consideration.
> >
> > Regards,
> >
> > Amine Aboufirass
> >
> > --
> > 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 [1][5]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
> > To view this discussion on the web visit [2][6]https://
> groups.google.com/d/msgid/
> > pandoc-discuss/
> > CAMwawgOpaV0jvJccC3zhnSWprWQ8d0qbvH1W8TRF1KObFYH9fA%[7]
> 40mail.gmail.com.
> >
> > References:
> >
> > [1] mailto:[8]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [2] [9]https://groups.google.com/d/msgid/pandoc-discuss/
> CAMwawgOpaV0jvJccC3zhnSWprWQ8d0qbvH1W8TRF1KObFYH9fA%40mail.gmail.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 [10]
> pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
> To view this discussion on the web visit [11]https://
> groups.google.com/d/msgid/pandoc-discuss/
> Yy2JG50GVYKtHDsA%40localhost.
>
> --
> 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 [12]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
> To view this discussion on the web visit [13]https://groups.google.com/
> d/msgid/pandoc-discuss/
> CAMwawgNJjZ%3DJB3751cmKvBB9GSQ-AuZ2f1oEwzjrbgg9qsW_kQ%40mail.gmail.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 [14]pandoc-discuss+unsubscribe@googlegroups.com.
> To view this discussion on the web visit [15]https://groups.google.com/d/
> msgid/pandoc-discuss/
> CADAJKhCYFW%3Dk9fxM6eLM782V3%2BsQ7_X9eH_7LfxO69z%3DDwjONg%40mail.gmail.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 [16]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
> To view this discussion on the web visit [17]https://groups.google.com/d/msgid/
> pandoc-discuss/
> CAMwawgOjpuNWqcFg7CAYansucXhp%2BF_mk2rdLCJ7K3-8Yzd_bQ%40mail.gmail.com.
>
> References:
>
> [1] mailto:bpj@melroch.se
> [2] mailto:amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> [3] mailto:amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
> [4] mailto:bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org
> [5] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [6] https://groups.google.com/d/msgid/
> [7] http://40mail.gmail.com/
> [8] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [9] https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgOpaV0jvJccC3zhnSWprWQ8d0qbvH1W8TRF1KObFYH9fA%40mail.gmail.com?utm_medium=email&utm_source=footer
> [10] mailto:pandoc-discuss%2Bunsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [11] https://groups.google.com/d/msgid/pandoc-discuss/Yy2JG50GVYKtHDsA%40localhost
> [12] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [13] https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgNJjZ%3DJB3751cmKvBB9GSQ-AuZ2f1oEwzjrbgg9qsW_kQ%40mail.gmail.com?utm_medium=email&utm_source=footer
> [14] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [15] https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhCYFW%3Dk9fxM6eLM782V3%2BsQ7_X9eH_7LfxO69z%3DDwjONg%40mail.gmail.com?utm_medium=email&utm_source=footer
> [16] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [17] https://groups.google.com/d/msgid/pandoc-discuss/CAMwawgOjpuNWqcFg7CAYansucXhp%2BF_mk2rdLCJ7K3-8Yzd_bQ%40mail.gmail.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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/YzHEkBq9r46iJAFG%40localhost.

To Bastien:

To Daniel: