emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: vertical space
Date: Fri, 31 Jan 2014 09:35:51 +0100	[thread overview]
Message-ID: <8761p0czvc.fsf@gmail.com> (raw)
In-Reply-To: <87d2j866rj.fsf@gmail.com> (Nick Dokos's message of "Fri, 31 Jan 2014 00:48:48 -0500")

Hello,

Nick Dokos <ndokos@gmail.com> 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

next prev parent reply	other threads:[~2014-01-31  8:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31  4:17 vertical space Rustom Mody
2014-01-31  5:48 ` Nick Dokos
2014-01-31  8:35   ` Nicolas Goaziou [this message]
2014-01-31  6:44 ` Rustom Mody
2014-01-31  8:16   ` Nicolas Goaziou
  -- strict thread matches above, loose matches on Subject: below --
2016-03-04 14:19 Vertical space Johann Spies
2016-03-04 14:25 ` Marcin Borkowski
2016-03-04 15:06   ` Johann Spies
2016-03-04 15:41     ` Marcin Borkowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8761p0czvc.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).