From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Prevent auto-filling of export snippets Date: Fri, 08 Dec 2017 16:46:43 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a11c1859e9f4222055fd6eea1" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53950) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eNLnc-000451-J5 for emacs-orgmode@gnu.org; Fri, 08 Dec 2017 11:46:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eNLnb-0000eQ-T4 for emacs-orgmode@gnu.org; Fri, 08 Dec 2017 11:46:56 -0500 Received: from mail-yb0-x22d.google.com ([2607:f8b0:4002:c09::22d]:34737) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eNLnb-0000dj-NL for emacs-orgmode@gnu.org; Fri, 08 Dec 2017 11:46:55 -0500 Received: by mail-yb0-x22d.google.com with SMTP id k4so4516562ybc.1 for ; Fri, 08 Dec 2017 08:46:55 -0800 (PST) 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: emacs-org list --001a11c1859e9f4222055fd6eea1 Content-Type: text/plain; charset="UTF-8" Hello, If I have a long Export Snippet like: @@html:This HTML Export Snippet will also get exported for Hugo exports, verbatim.@@ and with auto-fill-mode enabled (70 cols), if I hit Enter at the end of the line, I becomes: @@html:This HTML Export Snippet will also get exported for Hugo exports, verbatim.@@ (If it is difficult to see the difference in email, auto-filling has inserted a hard line break before the "exports, verbatim.@@" part in the second snippet above.) So then, obviously, that auto-filled export snippet doesn't get parsed by Org as an Export Snippet. Can the rules in Org set to prevent auto-filling (like in Headings) be set for Export Snippets too? I am using the master branch, but I believe the same issue would be on maint too. Thanks. -- Kaushal Modi --001a11c1859e9f4222055fd6eea1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

If I have a l= ong Export Snippet like:

@@html:This HTML <b>Export Snippet<= ;/b> will also get exported for Hugo exports, <code>verbatim</c= ode>.@@

and with auto-fill-mode enabled (70 cols), if I hit= Enter at the end of the line, I becomes:

@@html:This HTML <b>= Export Snippet</b> will also get exported for Hugo
exports, <co= de>verbatim</code>.@@

(If it is difficult to see the = difference in email, auto-filling has inserted a hard line break before the= "exports, <code>verbatim</code>.@@" part in the seco= nd snippet above.)

So then, obviously, that auto-filled export= snippet doesn't get parsed by Org as an Export Snippet.
=
Can the rules in Org set to prevent auto-filling (like in He= adings) be set for Export Snippets too?

I am using= the master branch, but I believe the same issue would be on maint too.

Thanks.

-- =

Kaushal Modi

--001a11c1859e9f4222055fd6eea1--