From: Nicolas Girard <nicolas.girard@nerim.net>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Re: [PATCH] Suppress extra newlines around source code in LaTeX export
Date: Tue, 15 Dec 2009 11:55:58 +0100 [thread overview]
Message-ID: <51b0095d0912150255n290a383dm1574a1b1c44c1b4a@mail.gmail.com> (raw)
In-Reply-To: <66D2118D-3D77-4034-AE7A-300CFB66CF48@gmail.com>
2009/12/14 Carsten Dominik <carsten.dominik@gmail.com>:
> Actually, I cannot reproduce this problem - I do not see the extra newline.
>
Hi Carsten,
you're absolutely right, I performed yet another git pull and couldn't
reproduce this either. Great !
Now, speaking of extra newlines, I'm puzzled about this: at some stage
(which I didn't identify yet, maybe when exporting to LaTeX), Org adds
an ID property to some headings in my document ; that is, for
instance,
* Aa
* Bb
Text
becomes
* Aa
* Bb
:PROPERTIES:
:ID: fa489059-d27e-47fb-929d-8ca9c749d079
:END:
Text
Notice the extra newline between :END: and Text. It's all good except
when exporting to LaTeX *and* the concerned heading is to be treated
as an item.
I've been thinking a bit about this special case ; and it seems to me
like, on one side, the extra newline should remain, and on the other
side, empty lines following a heading should be ignored by the LaTeX
translator when this heading is translated into an item.
What do you think ?
--
Nicolas
next prev parent reply other threads:[~2009-12-15 10:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 21:03 [PATCH] Suppress extra newlines around source code in LaTeX export Nicolas Girard
2009-12-03 14:42 ` Carsten Dominik
2009-12-05 11:58 ` Nicolas Girard
2009-12-09 10:00 ` Carsten Dominik
2009-12-09 22:21 ` Nicolas Girard
2009-12-10 21:37 ` Nicolas Girard
2009-12-14 15:41 ` Carsten Dominik
2009-12-15 10:55 ` Nicolas Girard [this message]
2009-12-16 10:48 ` Carsten Dominik
2009-12-09 22:50 ` Nicolas Girard
2009-12-09 23:56 ` Nicolas Girard
2009-12-10 8:08 ` Carsten Dominik
2009-12-10 21:38 ` Nicolas Girard
2009-12-10 8:08 ` Carsten Dominik
2009-12-10 21:39 ` Nicolas Girard
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=51b0095d0912150255n290a383dm1574a1b1c44c1b4a@mail.gmail.com \
--to=nicolas.girard@nerim.net \
--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 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).