From mboxrd@z Thu Jan 1 00:00:00 1970 From: Trey Ethan Harris Subject: Re: Long links Date: Sat, 4 Jan 2020 17:35: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="000000000000161ef8059b580cae" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:50502) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ins1N-0007lZ-Su for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 17:35:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ins1M-0001di-9n for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 17:35:49 -0500 Received: from mail-lj1-x22f.google.com ([2a00:1450:4864:20::22f]:38104) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ins1L-0001UH-U8 for emacs-orgmode@gnu.org; Sat, 04 Jan 2020 17:35:48 -0500 Received: by mail-lj1-x22f.google.com with SMTP id w1so25273253ljh.5 for ; Sat, 04 Jan 2020 14:35: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 , emacs-orgmode@gnu.org Cc: mail@nicolasgoaziou.fr --000000000000161ef8059b580cae Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If you won=E2=80=99t take a possible XY problem answer amiss: In general, I= =E2=80=99ve found it much easier to use visual-line-mode than to worry about all this=E2=80=94in fact, I have visual-line-mode set to automatically engage i= n org-mode. 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 w= ith 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=E2=80=94it rewraps and centers the column of text (not centering every l= ine, 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=E2=80=99s 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=E2=80=99s are j= ust present in their original forms. On Sat, Jan 4, 2020 at 16:58 Steven Penny 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? > > --000000000000161ef8059b580cae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
If you won=E2=80=99t take a possible XY problem= answer amiss: In general, I=E2=80=99ve found it much easier to use visual-= line-mode than to worry about all this=E2=80=94in fact, I have visual-line-= mode set to automatically engage in org-mode. At some point in 2016 I see f= rom my Git history that I un-filled all my Org files (i.e., changed =E2=80= =9Cparagraphs=E2=80=9D interspersed with newlines near fill-column to a sin= gle line per paragraph no matter how long it is), so for some ten years bef= ore 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=E2=80=94it rewraps and c= enters 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 f= ullscreen Emacs is about 166 characters wide; if I have a single window ope= n I get 70-char-width lines in the middle of the screen; if I have two wind= ows open side-by-side, they each get a column margin.

In cases like this, these solutions result in= long URL=E2=80=99s getting interrupted by backlashes in the rightmost colu= mn in display, but in the original file (and if you kill copy by region) th= e long URL=E2=80=99s 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: >
>=C2=A0 =C2=A0 Org recognizes plain URIs, possibly wrapped within angle<= br> >=C2=A0 =C2=A0 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 schem= es. 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-m= ode/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?

--000000000000161ef8059b580cae--