From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/13023 Path: news.gmane.org!not-for-mail From: Ophir Lifshitz Newsgroups: gmane.text.pandoc Subject: Re: Add a newline after a LineBreak to writers? Date: Thu, 18 Jun 2015 10:31:15 -0700 (PDT) Message-ID: <5919c781-f48e-4453-8c99-e2456c43b877@googlegroups.com> References: <20150204175703.GA25676@localhost.hsd1.ca.comcast.net> <20150205035235.GA27289@localhost.hsd1.ca.comcast.net> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_17_1160647421.1434648675434" X-Trace: ger.gmane.org 1434648691 24075 80.91.229.3 (18 Jun 2015 17:31:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 18 Jun 2015 17:31:31 +0000 (UTC) To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-X-From: pandoc-discuss+bncBDM4PRVZZYLBBZEARSWAKGQEDDURGQA-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Thu Jun 18 19:31:20 2015 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane.org Original-Received: from mail-ig0-f183.google.com ([209.85.213.183]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Z5den-0000AK-FC for gtp-pandoc-discuss@m.gmane.org; Thu, 18 Jun 2015 19:31:17 +0200 Original-Received: by igdh15 with SMTP id h15sf187175igd.0 for ; Thu, 18 Jun 2015 10:31:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :content-type:x-original-sender:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe; bh=myngbeonOF7sbjgdAJa1FrU1An8HElhsFwA1alD1TAk=; b=TiSIGeGribZdrfeodKVDpLpN6/gOrYnjWqwabAlMPOTt/JptCUt/sv3aEFTShKiH5V RIua7VA/kgE1mcsSGuLEi0DbZaN+KvN3oOJfl0/0CdZJ4DRfpKb8pCCJPNb6vKfkWoE8 DIzr8l7ihFOiBnGn4betH5vHI+jGl8BiTk1eX/myqt9UKHMaMInaIhWybMc6MKZ5X0y/ Ms7Vz0tJmFUDqUFJBZumLrrnYwWAbXALzMzByfgcWeBq9b/ozfa6P6s5pyasE+zJtJEy bfqy9xegCZ0ymt2kUaIKFq52gI6d0Eu+1Ey+H24tvCzyu7h5gInQPNXpQMnjQ7a4JJ6A aiCQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :content-type:x-original-sender:reply-to:precedence:mailing-list :list-id:x-spam-checked-in-group:list-post:list-help:list-archive :sender:list-subscribe:list-unsubscribe; bh=myngbeonOF7sbjgdAJa1FrU1An8HElhsFwA1alD1TAk=; b=jU0XocqXt48ykDdAyjd6rA7MxDmxIvPYbW0h+tv2nAEpst+zM/Ou54qxcvzVsHdzGc NvdALWkF1F0y/AfEjnTNSIUbUTKhEdr0lW0sSOLhEM3HQn9g8Peb4JzVaWChJ7+lWiCw fc/yf0JO7pcFjq3ynJDbz/orSUyLLiGJMmVIOhpKHkKAn7S5mgEGi5+Rr5+6e4xkAL1g faqK7Yvv2rv6SzYJIWShXscJvcrFkrETFBDKx/Jd9nytIO6gSxBBoagOGeAT+SsAs66r +NGBQTnOPVSDy6DeKBZvPOdogPjIKGwBdvQ+VmlLX19RG78myhyZ38El1VrCfoTy3qGV 2V6A== X-Received: by 10.140.85.11 with SMTP id m11mr238555qgd.29.1434648676299; Thu, 18 Jun 2015 10:31:16 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 10.140.104.245 with SMTP id a108ls1638416qgf.76.gmail; Thu, 18 Jun 2015 10:31:15 -0700 (PDT) X-Received: by 10.140.109.35 with SMTP id k32mr140047qgf.34.1434648675873; Thu, 18 Jun 2015 10:31:15 -0700 (PDT) In-Reply-To: X-Original-Sender: hangfromthefloor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Spam-Checked-In-Group: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Xref: news.gmane.org gmane.text.pandoc:13023 Archived-At: ------=_Part_17_1160647421.1434648675434 Content-Type: multipart/alternative; boundary="----=_Part_18_1407239046.1434648675434" ------=_Part_18_1407239046.1434648675434 Content-Type: text/plain; charset=UTF-8 Just wondering, was this the only discussion prior to https://github.com/jgm/pandoc/pull/1925 landing? Thanks. On Thursday, February 5, 2015 at 12:08:40 AM UTC-5, Tim Lin wrote: > > all right, will get something going tonight > > On Wednesday, 4 February 2015 19:52:52 UTC-8, John MacFarlane wrote: >> >> OK, let's just make it insensitive to `--no-wrap`, with a line break >> either way. >> >> +++ Tim Lin [Feb 04 15 17:42 ]: >> >The no wrap thing sounds sensible, although I really have no idea >> whether >> >more people expect the whole block to be unwrapped or just the >> individual >> >lines. >> > >> >Personally I would expect `--no-wrap` output to be useful for editing >> >without needing text reflowing functionality. With that assumption, >> >unwrapping individual lines but breaking at the LineBreaks seems to me >> to >> >be the most friendly behavior for editing. >> > >> > >> >On Wednesday, 4 February 2015 09:57:18 UTC-8, John MacFarlane wrote: >> >> >> >> 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-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org . >> >> >To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@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. >> >> >> >> >> > >> >-- >> >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 post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org >> >To view this discussion on the web visit >> https://groups.google.com/d/msgid/pandoc-discuss/eef791a5-f76f-4e98-a2bc-0e63c79bc7db%40googlegroups.com. >> >> >For more options, visit https://groups.google.com/d/optout. >> >> -- 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/5919c781-f48e-4453-8c99-e2456c43b877%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. ------=_Part_18_1407239046.1434648675434 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Just wondering, was this the only discussion prior to http= s://github.com/jgm/pandoc/pull/1925 landing?

Thanks.
=
On Thursday, February 5, 2015 at 12:08:40 AM UTC-5, Tim Lin wrote:
all right, will ge= t something going tonight

On Wednesday, 4 February 2015 19:52:52 UTC= -8, John MacFarlane wrote:
OK, let'= s just make it insensitive to `--no-wrap`, with a line break either way.

+++ Tim Lin [Feb 04 15 17:42 ]:
>The no wrap thing sounds sensible, although I really have no idea w= hether
>more people expect the whole block to be unwrapped or just the indi= vidual
>lines.
>
>Personally I would expect `--no-wrap` output to be useful for editi= ng
>without needing text reflowing functionality. With that assumption,
>unwrapping individual lines but breaking at the LineBreaks seems to= me to
>be the most friendly behavior for editing.
>
>
>On Wednesday, 4 February 2015 09:57:18 UTC-8, John MacFarlane wrote= :
>>
>> I think this is a good idea.  (But maybe we should make i= t 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 lo= oking in LaTeX:
>> >
>> >\texttt{\ 1.}~\textbf{Inputs}:~variables~$A, b$\\\tex= ttt{\
>> >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{u= ntil}~$n$~\textbf{do}\\\texttt{\
>>
>> >8.}~~~~~~~~~~~~\textbf{if}~$j \ne i$~\textbf{then}\\\textt= t{\
>> >9.}~~~~~~~~~~~~~~~$\sigma \leftarrow \sigma + a_{ij}
>> >\phi_j$\\\texttt{10.}~~~~~~~~~~~~\textbf{end~if}\\\te= xttt{11.}~~~~~~~~\textbf{end}~($j$-loop)\\\texttt{12.}~~~~~~~~$\<= wbr>phi_i
>>
>> >\leftarrow \frac 1 {a_{ii}} (b_i -
>> >\sigma)$\\\texttt{13.}~~~~\textbf{end}~($i$-loop)\\\<= wbr>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 s= pecial case
>> where
>> >the usage of LineBreak can easily get out of control.
>> >
>> >I wonder if it's better to add a newline after each LineBr= eak inline
>> >element. I'm really just targeting line-blocks, but as the= y don't have
>> >their own block-level type the only alternative is to chan= ge 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~s= olution\\
>> >\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{u= ntil}~$n$~\textbf{do}\\
>>
>> >\texttt{\ 8.}~~~~~~~~~~~~\textbf{if}~$j \ne i$~\textbf{the= n}\\
>> >\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 th= e Google Groups
>> "pandoc-discuss" group.
>> >To unsubscribe from this group and stop receiving emails f= rom it, send an
>> email to pandoc-discus...@googlegroups.com <jav= ascript:>.
>> >To post to this group, send email to pandoc-...@googleg= roups.com
>> <javascript:>.
>> >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.
>>
>>
>
>--=20
>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, s= end an email to pandoc-discus...@googlegroups.com<= /a>.
>To post to this group, send email to pandoc-...= @googlegroups.com.
>To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/eef791a5-f76f-4e98-a2bc-0e63c79bc7db%40goog= legroups.com.
>For more options, visit https://groups.google.com/d/o= ptout.

--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to pand= oc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/= msgid/pandoc-discuss/5919c781-f48e-4453-8c99-e2456c43b877%40googlegroups.co= m.
For more options, visit http= s://groups.google.com/d/optout.
------=_Part_18_1407239046.1434648675434-- ------=_Part_17_1160647421.1434648675434--