From: Trey Ethan Harris <treyharris@gmail.com>
To: Steven Penny <svnpenn@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Long links
Date: Sat, 4 Jan 2020 18:08:34 -0500 [thread overview]
Message-ID: <CALKJ+Eusqs1v50tSr1SqGo2_mpw=USnu+G5yV+PoNX-hxDUJ4g@mail.gmail.com> (raw)
In-Reply-To: <CAAXzdLVJwTunP+bziF9buS8+NEQz4bfTWFo6vCkR04g6g4WU2g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]
On Sat, Jan 4, 2020 at 17:56 Steven Penny <svnpenn@gmail.com> 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 “paragraphs” interspersed with newlines 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 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 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 “Nope”—I don’t publish the Org files I’m
talking about, but I could show you some sample diffs if you don’t 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’ ordinary behavor (which is what I want if I ever publish the code),
and prose text is stored in “paragraph, 2 × newlines, paragraph, 2 ×
newlines, paragraph” form—which ,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’ve found a distressingly high proportion of
comments parsers can’t deal with newline-wrapped text and turns each
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—blocks get post processed by content-aware dedicated
exporters, while interstitial text may or may not—but it’s at least always
in a form that 95% of the time can just be cut-and-paste, if nothing else.
[-- Attachment #2: Type: text/html, Size: 2350 bytes --]
next prev parent reply other threads:[~2020-01-04 23:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 20:51 Long links Steven Penny
2019-12-30 2:08 ` Nicolas Goaziou
2019-12-30 4:13 ` Steven Penny
2019-12-30 8:55 ` Nicolas Goaziou
2020-01-04 15:36 ` Steven Penny
2020-01-04 17:44 ` Nicolas Goaziou
2020-01-04 21:58 ` Steven Penny
2020-01-04 22:35 ` Trey Ethan Harris
2020-01-04 22:56 ` Steven Penny
2020-01-04 23:08 ` Trey Ethan Harris [this message]
2020-01-04 23:26 ` Steven Penny
2020-01-05 0:18 ` Trey Ethan Harris
2020-01-05 0:23 ` Steven Penny
2020-01-05 0:45 ` Trey Ethan Harris
2020-01-05 0:59 ` Steven Penny
2020-01-05 2:13 ` Trey Ethan Harris
2020-01-05 2:57 ` Steven Penny
2020-01-05 6:25 ` Adam Porter
2020-01-05 8:03 ` Fraga, Eric
2020-01-05 14:02 ` Steven Penny
2020-01-05 16:08 ` Eduardo Ochs
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALKJ+Eusqs1v50tSr1SqGo2_mpw=USnu+G5yV+PoNX-hxDUJ4g@mail.gmail.com' \
--to=treyharris@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=svnpenn@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).