From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rustom Mody Subject: Re: vertical space Date: Fri, 31 Jan 2014 12:14:55 +0530 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b2e45263c321204f13e845f Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44854) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W97qn-000601-U4 for emacs-orgmode@gnu.org; Fri, 31 Jan 2014 01:45:18 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W97qn-0008Lk-1k for emacs-orgmode@gnu.org; Fri, 31 Jan 2014 01:45:17 -0500 Received: from mail-pa0-x232.google.com ([2607:f8b0:400e:c03::232]:45071) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W97qm-0008Le-Ph for emacs-orgmode@gnu.org; Fri, 31 Jan 2014 01:45:16 -0500 Received: by mail-pa0-f50.google.com with SMTP id kp14so4070126pab.23 for ; Thu, 30 Jan 2014 22:45:15 -0800 (PST) In-Reply-To: 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: emacs-orgmode --047d7b2e45263c321204f13e845f Content-Type: text/plain; charset=ISO-8859-1 Nick wrote: > 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. So the question remains: How to get generic, consistent vertical space? --047d7b2e45263c321204f13e845f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Nick wrote:
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 lin= e
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<= br>rough description and not quite right in all particulars, but I hope
= it's close enough.

So the ques= tion remains: How to get generic, consistent vertical space?
--047d7b2e45263c321204f13e845f--