emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Thomas Holst <thomas.holst@de.bosch.com>
Cc: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Re: [new exporter] fails on double backslashes
Date: Tue, 17 Jul 2012 12:12:21 +0200	[thread overview]
Message-ID: <87ehoa66ii.fsf@gmail.com> (raw)
In-Reply-To: <ywod7gu2iwpt@de.bosch.com> (Thomas Holst's message of "Tue, 17 Jul 2012 11:05:34 +0200")


Thomas Holst <thomas.holst@de.bosch.com> writes:

> right now I am testing the new exporter. It works very well except on
> backslashes. Here is a minimal example which shows the problem:

Indeed. It chokes on line break. It should be fixed now.

Thank you for testing the new exporter and reporting this bug.


Nicolas Goaziou

      reply	other threads:[~2012-07-17 10:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17  9:05 [new exporter] fails on double backslashes Thomas Holst
2012-07-17 10:12 ` Nicolas Goaziou [this message]

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:

  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=87ehoa66ii.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=thomas.holst@de.bosch.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


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).