emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Pierfranco Minsenti <pierfranco.minsenti@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problems with Org Mode which doesn't properly manage linebreaks in LaTeX export
Date: Sun, 3 Jan 2010 18:55:48 +0100	[thread overview]
Message-ID: <5F9FB5CE-DB51-4AA0-A650-655A718E1040@gmail.com> (raw)
In-Reply-To: <4bec4eb31001030851j1595fa0fm37e9cf661abc0529@mail.gmail.com>


Hi Pierfranco,

please augment your report with example input (.org file) and
output (.tex file).

Thanks.

- Carsten

On Jan 3, 2010, at 5:51 PM, Pierfranco Minsenti wrote:

> Hi all,
>
> this is my 1st message to the list and I am writing to ask for help.
> I have a problem with the LaTeX export features of Org Mode, version  
> 6.27a. installed on a GNU Emacs Emacs 22.1.1 (powerpc-apple- 
> darwin7.9.0, Carbon Version 1.6.0).
>
> The problem is the folllowing: in the header lines of the LaTeX file  
> exported from an original Org file, the different commands which are  
> automatically addedd by the system and which should begin each of  
> them on a new paragraph, appear all in a single multiline paragraph.  
> The problem is that this paragraph is commented, because it begins  
> with the % Created 2010-01-03 etc. also added by the system.
> Perhaps this is also why the the PDF export doen't work.
>
> Another problem, caused by a line break not properly managed, is  
> related to bulleted lists when they are exported to a LaTeX file:  
> when items are longer that a single line, the lines after the first  
> are broken down (that is: the second line etc. begin a new, not- 
> bulleted paragraph, and they are not the second line of the item).
>
> I have set the variable Org Export Preserve Breaks to on (non-nil)  
> but nothing has changed.
>
> I have also checked the specific LaTeX export variables of Org but  
> all seems properly setted.
> By the way, when I make a very similar export from another Emacs  
> mode, that is Muse Mode, to LaTeX, I don't have these problems and  
> everything works just fine.
>
> Has anybody experienced this problem with Org Mode and could help me?
>
> Thank you very much in advance.
>
> pierfranco
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

- Carsten

  reply	other threads:[~2010-01-03 17:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-03 16:51 Problems with Org Mode which doesn't properly manage linebreaks in LaTeX export Pierfranco Minsenti
2010-01-03 17:55 ` Carsten Dominik [this message]
2010-01-03 18:30   ` Pierfranco Minsenti
2010-01-03 18:37     ` Carsten Dominik
2010-01-03 19:10       ` Pierfranco Minsenti
2010-01-03 19:14         ` Carsten Dominik
2010-01-03 20:05           ` Pierfranco Minsenti

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=5F9FB5CE-DB51-4AA0-A650-655A718E1040@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=pierfranco.minsenti@gmail.com \
    /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).