From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brent Goodrick Subject: Re: Bug: Prevent fill-paragraph from breaking inside Org mode links [9.1.9 (release_9.1.9-580-g39837b @ /home/drunkard/emacs_lisp_imported/org-mode/org-mode/lisp/)] Date: Mon, 09 Apr 2018 19:29:39 +0000 Message-ID: References: <23242.14979.666606.8006@bgnetgear2.ddns.net> <87efjp1wes.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000f0b71b05696f6dfc" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60912) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f5cUD-0008UL-DQ for emacs-orgmode@gnu.org; Mon, 09 Apr 2018 15:29:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f5cUC-00018U-8G for emacs-orgmode@gnu.org; Mon, 09 Apr 2018 15:29:53 -0400 Received: from mail-lf0-x236.google.com ([2a00:1450:4010:c07::236]:44445) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f5cUB-000180-Vj for emacs-orgmode@gnu.org; Mon, 09 Apr 2018 15:29:52 -0400 Received: by mail-lf0-x236.google.com with SMTP id g203-v6so8214404lfg.11 for ; Mon, 09 Apr 2018 12:29:51 -0700 (PDT) In-Reply-To: <87efjp1wes.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org --000000000000f0b71b05696f6dfc Content-Type: text/plain; charset="UTF-8" Hi Nicolas, All of that sounds reasonable. Thanks for the reply. -Brent On Sun, Apr 8, 2018, 9:43 AM Nicolas Goaziou wrote: > Hello, > > Brent Goodrick writes: > > > First, it may be a separate "bug" that org-return cannot recognize the > > multi-line Org link. > > Fixed. Thank you. > > > I don't know one way or the other for that, but instead I am arguing > > that org mode's fill paragraph function should never break the line > > right in the middle of the link. > > I disagree. Link descriptions can be arbitrarily long and Org should be > able to fill them. We could improve the fontification, however (e.g., > not using link face on blanks at the beginning of a line). > > > Instead the whole link should be treated as a word. To illustrate the > > fix, I have appended my own function to `fill-nobreak-predicate' to > > prevent the breakages > > I think this is the way to go: prevent filling in your own config. > > > Regards, > > -- > Nicolas Goaziou > --000000000000f0b71b05696f6dfc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Nicolas,

All of that sounds reasonable.=C2=A0 Thanks for the reply.

-Brent=C2=A0



On Sun, Apr 8, 2018, 9:43 AM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
Hello,

Brent Goodrick <bgoodr@gmail.com> writes:

> First, it may be a separate "bug" that org-return cannot rec= ognize the
> multi-line Org link.

Fixed. Thank you.

> I don't know one way or the other for that, but instead I am argui= ng
> that org mode's fill paragraph function should never break the lin= e
> right in the middle of the link.

I disagree. Link descriptions can be arbitrarily long and Org should be
able to fill them. We could improve the fontification, however (e.g.,
not using link face on blanks at the beginning of a line).

> Instead the whole link should be treated as a word. To illustrate the<= br> > fix, I have appended my own function to `fill-nobreak-predicate' t= o
> prevent the breakages

I think this is the way to go: prevent filling in your own config.


Regards,

--
Nicolas Goaziou
--000000000000f0b71b05696f6dfc--