public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: A A <amine.aboufirass-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Long inline code blocks forcing new lines in rendered html with pandoc markdown
Date: Fri, 11 Feb 2022 02:10:47 -0800 (PST)	[thread overview]
Message-ID: <066754e7-85c0-4571-a088-082f9cb8f2d4n@googlegroups.com> (raw)
In-Reply-To: <55ec4b54-6494-4d86-a68a-0f0e2ef598b4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

Never mind. It looks like `pandoc` *does* ignore the linebreaks between the 
backtick characters. The `max-width` property in the CSS for the `body` 
element was very narrow in the result html, which gave me the impression 
that it was breaking up my inline code. Deactivating the `max-width` in my 
resulting html styling showed me that the verbatim line was in fact intact.

On Friday, February 11, 2022 at 10:42:07 AM UTC+1 A A wrote:

> Suppose I have very long inline code in my markdown document:
>
> `javac -d classes catching_handling\GenerateIndexOutOfBoundsException.java`
>
> To keep my markdown clean, I would like for my lines to not go over 69 
> characters in Vim. The command above has more characters than that.
>
> If I were dealing with regular text, simply starting a new line in the 
> markdown will not force a newline in the rendered html document:
>
> javac -d classes
> catching_handling\GenerateIndexOutOfBoundsException.java
>
>
> However if I do the following in Vim:
>
> `javac -d classes 
> catching_handling\GenerateIndexOutOfBoundsException.java`
>
>
> The inline code in the rendered html does have a line break, which I don't 
> want.
>
> How do I keep my markdown clean and still use long inline code like the 
> example above in markdown?
>

-- 
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/066754e7-85c0-4571-a088-082f9cb8f2d4n%40googlegroups.com.

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

      parent reply	other threads:[~2022-02-11 10:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11  9:42 A A
     [not found] ` <55ec4b54-6494-4d86-a68a-0f0e2ef598b4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-02-11 10:10   ` A A [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=066754e7-85c0-4571-a088-082f9cb8f2d4n@googlegroups.com \
    --to=amine.aboufirass-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).