Org not preserving Python indent levels on LaTex export due to tabs

Org not preserving Python indent levels on LaTex export due to tabs

[James Ryland Miller]

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

Here's a test.org file:

* Heading 1

LaTeX export does not work on python src blocks with more than 2
levels of indentation.

For example (4 spaces per indent level, not tabs):

#+BEGIN_SRC python -n
      def foo(x):
          print("Hi: %s" % x)
          if x == "James":
              print("James is the best!")
          else:
              return x
#+END_SRC

The above should be indented properly. But it isn't. The resulting
.tex file has tabs on the second indent level lines and the tab
doesn't even line up with the 4 spaces per tab either. Any ideas how
to get rid of this? If I run a =C-x h M-x untabify= on the .tex file,
then it exports just fine. But I don't /want/ to do that each and
every time I export my org files.

Here's the verbatim portion of the generated LaTeX source:

#+BEGIN_SRC latex -n

\begin{verbatim}
1  def foo(x):
2      print("Hi: %s" % x)
3      if x == "James":
4   print("James is the best!")
5      else:
6   return x
\end{verbatim}
#+END_SRC

Note: lines 4 and 6 in the =\begin{verbatim}= blocks.

Line 4 is "4[space][space][tab]print("James...")"  How do I get org to export
with all spaces and no tabs for verbatims in LaTeX?

Re: Org not preserving Python indent levels on LaTex export due to tabs

[Nicolas Goaziou]

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

Re: Org not preserving Python indent levels on LaTex export due to tabs

[James Ryland Miller]

Thank you! That worked perfectly. Is '-i' not in the docs?

On Sun, Feb 2, 2014 at 1:49 AM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> 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

Re: Org not preserving Python indent levels on LaTex export due to tabs

[John Hendy]

I think it was very recently added (i.e. yesterday) due to this thread
about a very similar (same) issue:
- http://www.mail-archive.com/emacs-orgmode@gnu.org/msg81203.html

I'd love to update Worg/documentation to include it... out of
curiosity, where were you looking for it to be documented? That way, I
can add it to the most intuitive/popular location.


Thanks,
John

On Sun, Feb 2, 2014 at 11:32 AM, James Ryland Miller
<james.ryland.miller@gmail.com> wrote:
> Thank you! That worked perfectly. Is '-i' not in the docs?
>
> On Sun, Feb 2, 2014 at 1:49 AM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>> 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
>

Re: Org not preserving Python indent levels on LaTex export due to tabs

[Sebastien Vauban]

Nicolas Goaziou wrote:
> James Ryland Miller <james.ryland.miller-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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.

Again (as for `org-src-fontify-natively'), shouldn't this be true by
default?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: Org not preserving Python indent levels on LaTex export due to tabs

[Bastien]

Hi Sébastien,

"Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:

> Again (as for `org-src-fontify-natively'), shouldn't this be true by
> default?

I don't know for other people, but the default value is good for me.

-- 
 Bastien

Re: Org not preserving Python indent levels on LaTex export due to tabs

[Samuel Wales]

i can't seem to find the -i flag in the manual.  perhaps i used the
wrong search term?  i looked in literal examples and in working with
source code.  i am using maint.

also:

  - is there another flag to set org-src-preserve-indentation to nil?
  - will -i still work if org-src.preserve-indentation is t?

thanks.

i'd be happy with a fixed 2-space indentation, but that is not
possible in current org.  i find org-src-preserve-indentation to cause
more issues than it improves, so i am going to transition to it being
t, which feels safer even though it is not the default and does not
have the 2 spaces.

samuel


On 2/2/14, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
> 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
>
>


-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  ANYBODY can get it.

Denmark: free Karina Hansen NOW.

Re: Org not preserving Python indent levels on LaTex export due to tabs

[Nicolas Goaziou]

Hello,

Samuel Wales <samologist@gmail.com> writes:

> i can't seem to find the -i flag in the manual.  perhaps i used the
> wrong search term?  i looked in literal examples and in working with
> source code.  i am using maint.

Indeed. It doesn't appear in the manual.

I don't use it. Maybe Someone using it can provide a patch for it.

> also:
>
>   - is there another flag to set org-src-preserve-indentation to nil?
>   - will -i still work if org-src.preserve-indentation is t?

No.

> i'd be happy with a fixed 2-space indentation, but that is not
> possible in current org.  i find org-src-preserve-indentation to cause
> more issues than it improves, so i am going to transition to it being
> t, which feels safer even though it is not the default and does not
> have the 2 spaces.

FWIW, I'm happy with `org-src-preserve-indentation' set to nil.

Anyway, if you think `org-src-preserve-indentation' needs improvement,
please provide a description (or ECM) of what you expect it to do.


Regards,

-- 
Nicolas Goaziou

Re: Org not preserving Python indent levels on LaTex export due to tabs

[Bastien]

Hi,

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Indeed. It doesn't appear in the manual.
>
> I don't use it. Maybe Someone using it can provide a patch for it.

I added one sentence about -i in the manual.

Thanks,

-- 
 Bastien