emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Several questions about beamer export
Date: Fri, 12 Jul 2013 03:13:00 -0400	[thread overview]
Message-ID: <87mwps45fn.fsf@gmail.com> (raw)
In-Reply-To: 874nc0we5z.fsf@free.fr

Julien Cubizolles <j.cubizolles@free.fr> writes:

> Nick Dokos <ndokos@gmail.com> writes:
>
>> Julien Cubizolles <j.cubizolles@free.fr> writes:
>>
>>> ...
>>> * All the headers I add end up on the same line when I define them like
>>>   in the following (even with an empty line).
>>>
>>>  #+LATEX_HEADER_EXTRA: \institute{My Institure}
>>>   
>>>  #+LATEX_HEADER:\usepackage{mypackage}
>>>
>>>  The LaTeX file produced is not very readable. How can I produce
>>>  linebreaks between different LATEX_HEADER entries ?
>>>
>>
>> You need to modify the code to get them: that's probably an omission
>> (ngz will probably respond in much more detail than I can). They are
>> only cosmetic of course, but if you have to have them, you can try
>> adding them in org-beamer-template around line 880:
>>
>> 	       (concat (plist-get info :latex-header)
>> 		       "\n"                                  
>> 		       (plist-get info :latex-header-extra)
>> 		       "\n"
>> 		       (plist-get info :beamer-header-extra)
>> 		       "\n")))
>
> Let's make it an improvement suggestion then: getting \usepackage{} and
> \date{} commands mixed in the LaTeX file isn't very nice.
>
>> The problem with this is that the newlines are added even if the
>> various items are empty, so you may end up with more newlines than
>> are necessary.
>
> I'd personally prefer having empty lines instead of everything on the
> same line.
>

While we are talking about cosmetic whitespace issues, let me also point
out that the default beamer class in ox-beamer contains unnecessary
indentation. Clearly, it's there to make the lisp code look prettier but
it makes the resulting latex code uglier. Should anybody care? Eh, I
don't know... I certainly don't feel strongly about it either way.

-- 
Nick

  reply	other threads:[~2013-07-12  7:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 21:55 Several questions about beamer export Julien Cubizolles
2013-07-12  3:21 ` Nick Dokos
2013-07-12  5:16   ` Julien Cubizolles
2013-07-12  7:13     ` Nick Dokos [this message]
2013-07-12  7:19       ` Nicolas Goaziou
2013-07-12  7:02 ` Nick Dokos
2013-07-12 15:05   ` Julien Cubizolles
2013-07-12 15:16     ` Nick Dokos
2013-07-12 16:45       ` Darlan Cavalcante Moreira
2013-07-12 17:14         ` Nick Dokos
2013-07-15  9:03         ` Julien Cubizolles
2013-07-15 13:05           ` Nick Dokos
2013-07-15 19:58             ` Julien Cubizolles
2013-09-03  8:31               ` Julien Cubizolles
2013-07-12  7:16 ` Nicolas Goaziou

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=87mwps45fn.fsf@gmail.com \
    --to=ndokos@gmail.com \
    --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).