emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Steven Penny <svnpenn@gmail.com>
To: Trey Ethan Harris <treyharris@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Long links
Date: Sat, 4 Jan 2020 16:56:18 -0600	[thread overview]
Message-ID: <CAAXzdLVJwTunP+bziF9buS8+NEQz4bfTWFo6vCkR04g6g4WU2g@mail.gmail.com> (raw)
In-Reply-To: <CALKJ+EsejUKvmBTw=GyMH3moUuuuypg5j6MmJjxAPbARf2gVAw@mail.gmail.com>

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.

  reply	other threads:[~2020-01-04 22:56 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 [this message]
2020-01-04 23:08             ` Trey Ethan Harris
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=CAAXzdLVJwTunP+bziF9buS8+NEQz4bfTWFo6vCkR04g6g4WU2g@mail.gmail.com \
    --to=svnpenn@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=treyharris@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).