emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: James Ryland Miller <james.ryland.miller@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org not preserving Python indent levels on LaTex export due to tabs
Date: Sun, 02 Feb 2014 08:49:43 +0100	[thread overview]
Message-ID: <874n4iq7hk.fsf@gmail.com> (raw)
In-Reply-To: <CADPbT+BU5GTeyvxczEai-zQNWs-sVsAzA+R+oxTcya17kU4KZg@mail.gmail.com> (James Ryland Miller's message of "Sat, 1 Feb 2014 17:56:59 -0600")

Hello,

James Ryland Miller <james.ryland.miller@gmail.com> writes:

> I'm having trouble with getting python source=code blocks to export to
> LaTeX properly. I've figured out what's going wrong: the exporter is
> inserting tab characters on lines with 2 or more indentation levels in
> python. If I use org to export to .tex first, and then untabify the
> .tex files, the indent levels are preserved (assuming the tabs
> correctly lined up with the corresponding python in the first place,
> which many times they don't).

Try to set `org-src-preserve-indentation' to a non-nil value (on a very
recent Org) or add a "-i" flag to you source block:

  #+BEGIN_SRC python -n -i
  ...
  #+END_SRC

This should prevent Org from touching indentation within the block.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2014-02-02  7:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-01 23:56 Org not preserving Python indent levels on LaTex export due to tabs James Ryland Miller
2014-02-02  7:49 ` Nicolas Goaziou [this message]
2014-02-02 17:32   ` James Ryland Miller
2014-02-02 18:05     ` John Hendy
2014-02-03 13:08   ` Sebastien Vauban
2014-02-03 14:56     ` Bastien
2014-02-14  0:32   ` Samuel Wales
2014-02-16 10:11     ` Nicolas Goaziou
2014-03-15  6:43       ` Bastien

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=874n4iq7hk.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=james.ryland.miller@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).