From mboxrd@z Thu Jan 1 00:00:00 1970 From: Trey Ethan Harris Subject: Re: Long links Date: Sat, 4 Jan 2020 18:08:34 -0500 Message-ID: References: <5e0911cd.1c69fb81.3d5f3.0029@mx.google.com> <87mubazht9.fsf@nicolasgoaziou.fr> <87woa7uneq.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000001684a7059b588289" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:42430) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1insXI-0001xK-OU for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 18:08:49 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1insXH-0005yK-Ec for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 18:08:48 -0500 Received: from mail-lj1-x230.google.com ([2a00:1450:4864:20::230]:32770) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1insXH-0005rb-3z for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 18:08:47 -0500 Received: by mail-lj1-x230.google.com with SMTP id y6so39259094lji.0 for ; Sat, 04 Jan 2020 15:08:47 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Steven Penny Cc: emacs-orgmode@gnu.org --0000000000001684a7059b588289 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Jan 4, 2020 at 17:56 Steven Penny wrote: > On Sat, Jan 4, 2020 at 4:35 PM Trey Ethan Harris wrote: > > At some point in 2016 I see from my Git history that I un-filled all my > Org > > files (i.e., changed =E2=80=9Cparagraphs=E2=80=9D interspersed with new= lines near > fill-column > > to a single line per paragraph no matter how long it is), so for some t= en > > years before that I was wrapping lines and just got tired of the hassle= . > > Nope. I have been dealing with long links for many years, since at least > 2011. > Last month I learned that both reStructuredText and AsciiDoc can deal wit= h > them > pretty easily. Now that I know this, I am more included to use Markups > that have > that capability. > Not sure what you mean by =E2=80=9CNope=E2=80=9D=E2=80=94I don=E2=80=99t pu= blish the Org files I=E2=80=99m talking about, but I could show you some sample diffs if you don=E2=80=99t = believe me for some reason... But my larger point was that for me, _stored_ line length (as opposed to displayed line length) should be dictated by export, not for some arbitrary purpose. By doing it this way, source blocks get wrapped according to their modes=E2=80=99 ordinary behavor (which is what I want if I ever publish the= code), and prose text is stored in =E2=80=9Cparagraph, 2 =C3=97 newlines, paragrap= h, 2 =C3=97 newlines, paragraph=E2=80=9D form=E2=80=94which ,for pretty much everything= except email these days, is what you want. A common purpose I put Org prose to is editing text I will post as web content, like in a forum; I=E2=80=99ve found a distressingly high proportio= n of comments parsers can=E2=80=99t deal with newline-wrapped text and turns eac= h 72-column line into a paragraph. But almost all of these treat blank lines delimiting paragraphs correctly. So storing my text this way requires the least post processing=E2=80=94blocks get post processed by content-aware de= dicated exporters, while interstitial text may or may not=E2=80=94but it=E2=80=99s = at least always in a form that 95% of the time can just be cut-and-paste, if nothing else. --0000000000001684a7059b588289 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Jan 4, 2020 at 17:56 Steven Penny <svnpenn@gmail.com> wrote:
On Sat, Jan 4, 2020 at 4:35 PM T= rey Ethan Harris wrote:
> At some point in 2016 I see from my Git history that I un-filled all m= y Org
> files (i.e., changed =E2=80=9Cparagraphs=E2=80=9D interspersed with ne= wlines near fill-column
> to a single line per paragraph no matter how long it is), so for some = ten
> years before that I was wrapping lines and just got tired of the hassl= e.

Nope. I have been dealing with long links for many years, since at least 20= 11.
Last month I learned that both reStructuredText and AsciiDoc can deal with = them
pretty easily. Now that I know this, I am more included to use Markups that= have
that capability.
Not sure what you mean by =E2=80= =9CNope=E2=80=9D=E2=80=94I don=E2=80=99t publish the Org files I=E2=80=99m = talking=C2=A0about, but I could show you some sample diffs if you don=E2=80= =99t believe me for some reason...

But my larger point was that for me, _stored_ line length (as op= posed to displayed line length) should be dictated by export, not for some = arbitrary purpose. By doing it this way, source blocks get wrapped accordin= g to their modes=E2=80=99 ordinary behavor (which is what I want if I ever = publish the code), and prose text is stored in =E2=80=9Cparagraph, 2 =C3=97= newlines, paragraph, 2 =C3=97 newlines, paragraph=E2=80=9D form=E2=80=94wh= ich ,for pretty much everything except email these days, is what you want.= =C2=A0

A common purpose = I put Org prose to is editing text I will post as web content, like in a fo= rum; I=E2=80=99ve found a distressingly high proportion of comments parsers= can=E2=80=99t deal with newline-wrapped text and turns each 72-column line= into a paragraph. But almost all of these treat blank lines delimiting par= agraphs correctly. So storing my text this way requires the least post proc= essing=E2=80=94blocks get post processed by content-aware dedicated exporte= rs, while interstitial text may or may not=E2=80=94but it=E2=80=99s at leas= t always in a =C2=A0form that 95% of the time can just be cut-and-paste, if= nothing else.
--0000000000001684a7059b588289--