From: Carsten Dominik <carsten.dominik@gmail.com>
To: Nicolas Girard <nicolas.girard@nerim.net>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Re: [PATCH] Suppress extra newlines around source code in LaTeX export
Date: Thu, 10 Dec 2009 09:08:53 +0100 [thread overview]
Message-ID: <1A1EF196-9F26-4325-BE02-A78896E32397@gmail.com> (raw)
In-Reply-To: <51b0095d0912091556m3121b9d4r4528889b03c46aa0@mail.gmail.com>
On Dec 10, 2009, at 12:56 AM, Nicolas Girard wrote:
> 2009/12/9 Nicolas Girard <nicolas.girard@nerim.net>:
>> 2009/12/9 Carsten Dominik <carsten.dominik@gmail.com>:
>>> Hi Nicolas,
>>>
>>> I need additional information with respect to this patch:
>>>
>>
>>>> diff --git a/lisp/org-latex.el b/lisp/org-latex.el
>>>> index ce697a3..18c2183 100644
>>>> --- a/lisp/org-latex.el
>>>> +++ b/lisp/org-latex.el
>>>> @@ -877,7 +877,7 @@ If NUM, export sections as numerical sections."
>>>> (delete-region (point-at-bol 0) (point))
>>>> (insert (format "\\begin{%s}\n"
>>>> (symbol-name org-export-latex-low-
>>>> levels))))
>>>> - (insert (format "\n\\item %s\\\\\n%s\n"
>>>> + (insert (format "\\item %s\n%s"
>>>> heading
>>>> (if label (format "\\label{%s}"
>>>> label) "")))
>>>> (insert (org-export-latex-content content))
>>>
>>> Why would you like to remove the "\\" as well? When itemize lists
>>> are used
>>> to format headlines, I think there should be a line break after
>>> the end of
>>> the original headline. Otherwise the text below the headline will
>>> flow into
>>> the headline. Or am I missing something here?
>>
>> I think you're right ; I may have been abused by what Adobe Reader
>> displayed when performing my tests, as I just discovered that, for
>> whatever reason, it doesn't always reload the pdf file when using
>> <Ctrl-r>
>>
>
> Actually I do remember why I considered removing the '\\' : take
> this document:
>
> #=============
> Level 1
>
> ** Level 2
>
> *** Level 3
>
> **** Level 4
> - itemized
> - list
> #=============
>
> Since "Level 4" is expressed as an item, the only way of getting the
> correct output is *not* to have any '\\' between "Level 4" and
> "itemized". That is, in LaTeX, not to have '\\' between
> \item Level 4
> and
> \begin{itemize} \item itemized \item list \end{itemize}
OK, I am catching this case now as well.
Let me know if it works all right now.
- Carsten
next prev parent reply other threads:[~2009-12-10 8:48 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
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 [this message]
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=1A1EF196-9F26-4325-BE02-A78896E32397@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicolas.girard@nerim.net \
/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).