public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Add a newline after a LineBreak to writers?
Date: Wed, 4 Feb 2015 09:57:03 -0800	[thread overview]
Message-ID: <20150204175703.GA25676@localhost.hsd1.ca.comcast.net> (raw)
In-Reply-To: <b25e52ed-107c-4f32-a128-b9b68c149ce4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

I think this is a good idea.  (But maybe we should make it sensitive to `--no-wrap`, and omit the newline if `--no-wrap`?)

+++ Tim Lin [Feb 03 15 17:46 ]:
>I'm using the line-block construct extensively fro writing pseudocode. It
>usually works great, but boy does the rendered output look ugly. Here's an
>example of what one of my typical algorithms can end up looking in LaTeX:
>
>\texttt{\ 1.}~\textbf{Inputs}:~variables~$A, b$\\\texttt{\
>2.}~\textbf{Output}:~$\phi$~~~~~~~~~~~~~~~~\texttt{//this\ is\ a\ comment}\texttt{\
>3.}~Choose~an~initial~guess~$\phi$~to~the~solution\\\texttt{\
>4.}~~\textbf{repeat}~until~convergence\\\texttt{\
>5.}~~~~\textbf{for}~$i$~\textbf{from}~1~\textbf{until}~$n$~\textbf{do}\\\texttt{\
>6.}~~~~~~~~$\sigma \leftarrow 0$\\\texttt{\
>7.}~~~~~~~~\textbf{for}~$j$~\textbf{from}~1~\textbf{until}~$n$~\textbf{do}\\\texttt{\
>8.}~~~~~~~~~~~~\textbf{if}~$j \ne i$~\textbf{then}\\\texttt{\
>9.}~~~~~~~~~~~~~~~$\sigma \leftarrow \sigma + a_{ij}
>\phi_j$\\\texttt{10.}~~~~~~~~~~~~\textbf{end~if}\\\texttt{11.}~~~~~~~~\textbf{end}~($j$-loop)\\\texttt{12.}~~~~~~~~$\phi_i
>\leftarrow \frac 1 {a_{ii}} (b_i -
>\sigma)$\\\texttt{13.}~~~~\textbf{end}~($i$-loop)\\\texttt{14.}~~~~check~if~convergence~is~reached\\\texttt{15.}~\textbf{end}~(repeat)
>
>It's serviceable, but really hard to play with for a human. The HTML writer
>doesn't far much better. I realize that line-block are a special case where
>the usage of LineBreak can easily get out of control.
>
>I wonder if it's better to add a newline after each LineBreak inline
>element. I'm really just targeting line-blocks, but as they don't have
>their own block-level type the only alternative is to change LineBreak
>behavior. The above example would then look like this:
>
>\texttt{\ 1.}~\textbf{Inputs}:~variables~$A, b$\\
>\texttt{\ 2.}~\textbf{Output}:~$\phi$~~~~~~~~~~~~~~~~\texttt{//this\ is\ a\
>comment}
>\texttt{\ 3.}~Choose~an~initial~guess~$\phi$~to~the~solution\\
>\texttt{\ 4.}~~\textbf{repeat}~until~convergence\\
>\texttt{\
>5.}~~~~\textbf{for}~$i$~\textbf{from}~1~\textbf{until}~$n$~\textbf{do}\\
>\texttt{\ 6.}~~~~~~~~$\sigma \leftarrow 0$\\
>\texttt{\
>7.}~~~~~~~~\textbf{for}~$j$~\textbf{from}~1~\textbf{until}~$n$~\textbf{do}\\
>\texttt{\ 8.}~~~~~~~~~~~~\textbf{if}~$j \ne i$~\textbf{then}\\
>\texttt{\ 9.}~~~~~~~~~~~~~~~$\sigma \leftarrow \sigma + a_{ij} \phi_j$\\
>\texttt{10.}~~~~~~~~~~~~\textbf{end~if}\\
>\texttt{11.}~~~~~~~~\textbf{end}~($j$-loop)\\
>\texttt{12.}~~~~~~~~$\phi_i \leftarrow \frac 1 {a_{ii}} (b_i - \sigma)$\\
>\texttt{13.}~~~~\textbf{end}~($i$-loop)\\
>\texttt{14.}~~~~check~if~convergence~is~reached\\\texttt{15.}~\textbf{end}~(repeat)
>
>I can't really think of any negative ramification off the top of my head.
>I'd appreciate any help thinking about whether this would break anything.
>
>-- 
>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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/b25e52ed-107c-4f32-a128-b9b68c149ce4%40googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.


  parent reply	other threads:[~2015-02-04 17:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04  1:46 Tim Lin
     [not found] ` <b25e52ed-107c-4f32-a128-b9b68c149ce4-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-02-04 17:57   ` John MacFarlane [this message]
     [not found]     ` <20150204175703.GA25676-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2015-02-05  1:42       ` Tim Lin
     [not found]         ` <eef791a5-f76f-4e98-a2bc-0e63c79bc7db-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-02-05  3:52           ` John MacFarlane
     [not found]             ` <20150205035235.GA27289-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2015-02-05  5:08               ` Tim Lin
     [not found]                 ` <b115520b-6af7-4fae-b95d-50a759c2ef5d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-06-18 17:31                   ` Ophir Lifshitz
     [not found]                     ` <5919c781-f48e-4453-8c99-e2456c43b877-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-06-18 17:40                       ` John MacFarlane

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=20150204175703.GA25676@localhost.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).