From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: [RFC] The "c" Org macro Date: Mon, 22 May 2017 13:39:43 +0000 Message-ID: References: <2ee94a64a94b46259b0da6e7d34675c9@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> <87y3u7o3dj.fsf@t3610> <87pofjtk4b.fsf@t3610> <2069df8c23bc43f3b04b6e203b96be9d@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> <87r2zvpyst.fsf@delle7240> <8760guib5i.fsf@nicolasgoaziou.fr> <87h90dh1pd.fsf@nicolasgoaziou.fr> <87tw4df6zr.fsf@nicolasgoaziou.fr> <87d1b1f318.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c1cd53a8be45205501d015a" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55432) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dCnYy-0005Bu-AN for emacs-orgmode@gnu.org; Mon, 22 May 2017 09:39:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dCnYx-0007WE-C2 for emacs-orgmode@gnu.org; Mon, 22 May 2017 09:39:56 -0400 Received: from mail-lf0-x234.google.com ([2a00:1450:4010:c07::234]:36860) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dCnYx-0007Vu-3n for emacs-orgmode@gnu.org; Mon, 22 May 2017 09:39:55 -0400 Received: by mail-lf0-x234.google.com with SMTP id h4so31399099lfj.3 for ; Mon, 22 May 2017 06:39:54 -0700 (PDT) In-Reply-To: <87d1b1f318.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 --94eb2c1cd53a8be45205501d015a Content-Type: text/plain; charset="UTF-8" On Mon, May 22, 2017 at 9:13 AM Nicolas Goaziou wrote: > This is a wrong approach. A macro doesn't separate paragraphs, but > belongs to them. IOW, you get the desired side-effect, but break > underlying syntax. > I agree A better way to solve this would to add a function to > `fill-nobreak-predicate', like we already do for > `org-fill-line-break-nobreak-p' or > `org-fill-paragraph-with-timestamp-nobreak-p'. > > I will add it to the "n" macro patch. > I didn't know of those. Thanks! -- Kaushal Modi --94eb2c1cd53a8be45205501d015a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, May 22= , 2017 at 9:13 AM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
This is a wrong approach. A macro doesn't separate paragraphs, = but
belongs to them. IOW, you get the desired side-effect, but break
underlying syntax.

I agree=C2=A0
<= div>
A better way to solve this would to add a function to
`fill-nobreak-predicate', like we already do for
`org-fill-line-break-nobreak-p' or
`org-fill-paragraph-with-timestamp-nobreak-p'.

I will add it to the "n" macro patch.

I didn't know of those. Thanks!=C2=A0
--

Kaushal Modi

--94eb2c1cd53a8be45205501d015a--