emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Preservation of white space in babel blocks, exporting to PDF
Date: Thu, 30 Jan 2014 23:58:05 -0600	[thread overview]
Message-ID: <CA+M2ft-4VP=BMS9U8X-JeiaWWwC8Lg0sF9nf3=UoZh036tU9eg@mail.gmail.com> (raw)

Greetings,


I'm sure this is just a variable I've overlooked, but I'm wondering if
it's possible to export code blocks as they appear, with whitespace
preserved for better formatting in the resultant LaTeX document (I'm
using Beamer in this case).

Currently, the leading spaces in my blocks seem to be mostly removed
(I might have 8 or so to keep options in R code aligned, and the block
exports with 1-2 instead).

If I used #+begin/end_example instead of #+begin/end_src, it works properly.

The closest I found in my googling for a solution/setting/variable was
the variable =org-src-preserve-indentation=, but that seems to only
have to do with tangling.


Thanks for any suggestions,
John

next             reply	other threads:[~2014-01-31  5:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31  5:58 John Hendy [this message]
2014-01-31  8:09 ` Preservation of white space in babel blocks, exporting to PDF Nicolas Goaziou
2014-01-31 22:16   ` John Hendy
2014-01-31 22:25     ` Nicolas Goaziou
2014-01-31 22:46       ` John Hendy
2014-01-31 23:04         ` Nicolas Goaziou
2014-01-31 23:16           ` John Hendy
2014-01-31 23:25             ` Andreas Leha
2014-02-01  4:08               ` John Hendy
2014-02-01  8:28                 ` Nicolas Goaziou
2014-02-01 17:54                   ` John Hendy
2014-02-01 20:27                     ` Nicolas Goaziou
2014-02-01 21:02                       ` Nicolas Goaziou
2014-02-02  1:33                       ` John Hendy
2014-02-02  8:45                         ` Nicolas Goaziou
2014-02-02 15:59                           ` John Hendy

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='CA+M2ft-4VP=BMS9U8X-JeiaWWwC8Lg0sF9nf3=UoZh036tU9eg@mail.gmail.com' \
    --to=jw.hendy@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

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).