From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: vertical space Date: Fri, 31 Jan 2014 09:35:51 +0100 Message-ID: <8761p0czvc.fsf@gmail.com> References: <87d2j866rj.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58437) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W99Zf-0000qB-6d for emacs-orgmode@gnu.org; Fri, 31 Jan 2014 03:35:51 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W99ZW-0004ID-Oc for emacs-orgmode@gnu.org; Fri, 31 Jan 2014 03:35:43 -0500 Received: from mail-ee0-x22d.google.com ([2a00:1450:4013:c00::22d]:45111) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W99ZW-0004I9-IB for emacs-orgmode@gnu.org; Fri, 31 Jan 2014 03:35:34 -0500 Received: by mail-ee0-f45.google.com with SMTP id b15so2048447eek.18 for ; Fri, 31 Jan 2014 00:35:33 -0800 (PST) In-Reply-To: <87d2j866rj.fsf@gmail.com> (Nick Dokos's message of "Fri, 31 Jan 2014 00:48:48 -0500") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nick Dokos Cc: emacs-orgmode@gnu.org Hello, Nick Dokos writes: > Why exactly the last one is parsed as a literal string and not as a line > break, I don't know. Nicolas will probably explain all. The only thing I > can say is that if there is something other than whitespace on the line > before the \\, it gets parsed as a line break; if there is only > whitespace (or nothing), it gets parsed as a string. That's probably a > rough description and not quite right in all particulars, but I hope > it's close enough. That's exactly that. I even added the following comment in `org-element-line-break-successor': ;; A line break can only happen on a non-empty line. I'm not sure why, though. It may have to do with the fact that there is no easy way to escape backslashes in Org (AFAIK). I think we can remove this rule if we first add a "bslash" (or some other name) entity in `org-entities'. Regards, -- Nicolas Goaziou