emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Trey Ethan Harris <treyharris@gmail.com>
To: Steven Penny <svnpenn@gmail.com>, emacs-orgmode@gnu.org
Cc: mail@nicolasgoaziou.fr
Subject: Re: Long links
Date: Sat, 4 Jan 2020 17:35:34 -0500	[thread overview]
Message-ID: <CALKJ+EsejUKvmBTw=GyMH3moUuuuypg5j6MmJjxAPbARf2gVAw@mail.gmail.com> (raw)
In-Reply-To: <CAAXzdLW0zmsWbcSb0Zy5ZZM+cW=qz38uo4XkMEN_tJk9=Ox85Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2320 bytes --]

If you won’t take a possible XY problem answer amiss: In general, I’ve
found it much easier to use visual-line-mode than to worry about all
this—in fact, I have visual-line-mode set to automatically engage in
org-mode. 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.

And when writing longer passages of prose, I also toggle olivetti-mode
on—it rewraps and centers the column of text (not centering every line,
just the column) in a wide window. My olivetti-mode width is set to 70
chars, so even though my fullscreen Emacs is about 166 characters wide; if
I have a single window open I get 70-char-width lines in the middle of the
screen; if I have two windows open side-by-side, they each get a column
margin.

In cases like this, these solutions result in long URL’s getting
interrupted by backlashes in the rightmost column in display, but in the
original file (and if you kill copy by region) the long URL’s are just
present in their original forms.

On Sat, Jan 4, 2020 at 16:58 Steven Penny <svnpenn@gmail.com> wrote:

> On Sat, Jan 4, 2020 at 11:44 AM Nicolas Goaziou wrote:
> > In a recent manual, the section "Link format" starts with:
> >
> >    Org recognizes plain URIs, possibly wrapped within angle
> >    brackets[fn:23], and activate them as clickable links.
> >
> > The example I gave you is an angle link.
>
> Yes, I do see that documentation now. I also see this:
>
> > [fn:23] Plain URIs are recognized only for a well-defined set of
> schemes. See
> > External Links. Unlike URI syntax, they cannot contain parenthesis or
> white
> > spaces, either. URIs within angle brackets have no such limitation.
>
> https://github.com/bzg/org-mode/blob/master/doc/org-manual.org#footnotes
>
> However what is troubling is that in both of these pages:
>
> - https://github.com/bzg/org-mode/blob/master/doc/org-guide.org
> - https://github.com/bzg/org-mode/blob/master/doc/org-manual.org
>
> not a single example is provided of this syntax. Perhaps one could be
> added for
> clarity?
>
>

[-- Attachment #2: Type: text/html, Size: 3132 bytes --]

  reply	other threads:[~2020-01-04 22:35 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 [this message]
2020-01-04 22:56           ` Steven Penny
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='CALKJ+EsejUKvmBTw=GyMH3moUuuuypg5j6MmJjxAPbARf2gVAw@mail.gmail.com' \
    --to=treyharris@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --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).