From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ethan Ligon <ligon@berkeley.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problem with org-export--delete-comments
Date: Thu, 17 Dec 2015 21:48:39 +0100 [thread overview]
Message-ID: <87h9jgrec8.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <loom.20151217T190821-8@post.gmane.org> (Ethan Ligon's message of "Thu, 17 Dec 2015 18:27:27 +0000 (UTC)")
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?
> A related problem: one can no longer have commented lines in (at least
> some) property drawers.
This is not possible indeed, per property drawers syntax. Also, I'd
rather not introduce comments in property drawers (I don't think this
was ever officially supported anyway).
> It seems to me that the correct solution would have org-export--delete-
> comments actually delete a single line comment, not replace it with \n, as
> was the case prior to the indicated commit.
>
> I gather that the change was introduced to deal with a bug observed by
> Samuel Wales (http://article.gmane.org/gmane.emacs.orgmode/102860; see also
> below). His problem example involved incorrectly truncated footnotes
> (these are deemed to end after two blank lines). But it seems to me that
> the correct solution to his example is to delete *both* the commented
> line and the following blank line.
Been there, done that. Your solution is not correct in all cases. E.g.,
with the following document
Paragra1
# comment
Paragraph2
removing both the comment and the blank line above gives you a single
paragraph, which doesn't match expectations.
> I regard this as a bug, but if it's not how do others deal with similar
> issues?
I have the feeling that there is no perfect solution here, and something
will break on one side or the other, anyway.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-12-17 20:47 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 [this message]
2015-12-17 22:12 ` Andreas Leha
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=87h9jgrec8.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=ligon@berkeley.edu \
/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.