From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Bug: Please make org-emphasis-regexp-components respect all whitespace [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)] Date: Fri, 15 Sep 2017 00:22:56 +0200 Message-ID: <87ingkex8f.fsf@nicolasgoaziou.fr> References: <87lglh9hmi.fsf@sc3d.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51591) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dscXE-0000da-FG for emacs-orgmode@gnu.org; Thu, 14 Sep 2017 18:23:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dscXD-0003OS-C2 for emacs-orgmode@gnu.org; Thu, 14 Sep 2017 18:23:00 -0400 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:52937) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dscXD-0003KK-5E for emacs-orgmode@gnu.org; Thu, 14 Sep 2017 18:22:59 -0400 In-Reply-To: <87lglh9hmi.fsf@sc3d.org> (Reuben Thomas's message of "Thu, 14 Sep 2017 20:59:01 +0100") 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: Reuben Thomas Cc: emacs-orgmode@gnu.org Hello, Reuben Thomas writes: > I currently have in my Emacs init: > > (setq org-emphasis-regexp-components ;; define before loading org > '("[:space:]('\"{" "-[:space:].,:!?;'\")}\\[" "[:space:]\r\n" "." 1= )) > > In other words, I added [:space:] to the BORDER pattern too. > > It would seem reasonable to have something like this be the default. In > particular, worg/dev/org-syntax.org already talks about =E2=80=9Cwhitespa= ce=E2=80=9D, > not specifically =E2=80=9Cspaces, tabs etc.=E2=80=9D. > > But, I wonder, is it a problem that [:space:] contains vertical > whitespace characters too? (I left =E2=80=9C\r\n=E2=80=9D in the BORDER p= attern as a > reminder that they are there on purpose, whereas PRE and POST previously > contained only space and tab, i.e. horizontal whitespace.) On the other > hand, since PRE and POST are anchored to the start and end of a line, > and the number of newlines is by default limited to 1, perhaps it=E2=80= =99s not > a problem? I don't think it is a problem with vertical spaces. IIRC, that change was request by someone else some months ago, but the request probably felt through the cracks. Anyway, I made that change to master branch. We'll see what happens. Thank you. --=20 Nicolas Goaziou