From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Problem with org-export--delete-comments
Date: Thu, 17 Dec 2015 22:12:32 +0000 [thread overview]
Message-ID: <oluvb7wiv1r.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87h9jgrec8.fsf@nicolasgoaziou.fr
Hi Nicolas and Ethan,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Ethan Ligon <ligon@berkeley.edu> writes:
>
>> I've long used the following construction for displayed equations in org
>> #
>> \[
>> u_i(c)=p_i\lambda
>> \]
>> #
>> which (i) gives nice space for reading equations in the org-source, and
>> (ii) nicely protects the display equation from (fill-paragraph) and
>> friends.
>>
>> However, exporting with this construction *stopped* working after commit
>> 53a4209; what happens now is that ox.el replaces the # with a blank line,
>> breaking my single paragraph into three.
>
> I see only one paragraph above. Could you elaborate a bit?
I think the problem is in the exported latex file rather than in the org
document. While the org document indeed has one paragraph the exported
latex file does not. I can reproduce this.
With this org document:
--8<---------------cut here---------------start------------->8---
* Test
I've long used the following construction for displayed equations in org
#
\[
u_i(c)=p_i\lambda
\]
#
which (i) gives nice space for reading equations in the org-source, and
(ii) nicely protects the display equation from (fill-paragraph) and
friends.
--8<---------------cut here---------------end--------------->8---
I get this latex doc (relevant part only):
--8<---------------cut here---------------start------------->8---
\section{Test}
\label{sec:orgheadline1}
I've long used the following construction for displayed equations in org
\[
u_i(c)=p_i\lambda
\]
which (i) gives nice space for reading equations in the org-source, and
(ii) nicely protects the display equation from (fill-paragraph) and
friends.
--8<---------------cut here---------------end--------------->8---
I agree that the paragraph should not be broken in the exported
document. There are also other use cases for comments inside
paragraphs.
[ ... ]
Regards,
Andreas
next prev parent reply other threads:[~2015-12-17 22:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 18:27 Problem with org-export--delete-comments Ethan Ligon
2015-12-17 20:48 ` Nicolas Goaziou
2015-12-17 22:12 ` Andreas Leha [this message]
2015-12-17 22:36 ` Nicolas Goaziou
2015-12-17 22:56 ` Andreas Leha
2015-12-18 1:07 ` Ethan Ligon
2015-12-18 20:50 ` Nicolas Goaziou
2015-12-18 0:59 ` Ethan Ligon
2015-12-20 9:31 ` Nicolas Goaziou
2015-12-21 2:04 ` Ethan Ligon
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=oluvb7wiv1r.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.org \
/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
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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.