Re: [O] Source Code Syntax Highlighting in Beamer slides

[Suvayu Ali]

On Mon, Apr 22, 2013 at 08:29:57AM +0200, Bastien wrote:
> Hi Suvayu,
> 
> Suvayu Ali  writes:
> 
> > Rest of the documentation is worked on at the moment.  Worg is a
> > community resource, so you can contribute too!  There was a recent (~1
> > month) post by Bastien outlining a procedure to mark deprecated
> > documentation on Worg.
> 
> Yes.  The idea is simply to use 
> 
> #+OrgVersion: 8.0 
> 
> in the head of the document if the document describes things that are
> for Org >=8.0, and a :OrgVersion: 8.0 (multi-valued) property for the
> subtrees that require a specific version.
> 
> It's not widely used and difficult to use retroactively, but might be
> a good habit to have from now on.

Okay cool.  Thanks for repeating it again.  One of the weekends I'll try
to go through the tutorials and add the properties as appropriate.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] Source Code Syntax Highlighting in Beamer slides

[Bastien]

Hi Suvayu,

Suvayu Ali  writes:

> Rest of the documentation is worked on at the moment.  Worg is a
> community resource, so you can contribute too!  There was a recent (~1
> month) post by Bastien outlining a procedure to mark deprecated
> documentation on Worg.

Yes.  The idea is simply to use 

#+OrgVersion: 8.0 

in the head of the document if the document describes things that are
for Org >=8.0, and a :OrgVersion: 8.0 (multi-valued) property for the
subtrees that require a specific version.

It's not widely used and difficult to use retroactively, but might be
a good habit to have from now on.

-- 
 Bastien

Re: [O] Source Code Syntax Highlighting in Beamer slides

[Suvayu Ali]

On Mon, Apr 22, 2013 at 01:03:28AM +0200, Alexander Baier wrote:
> Nicolas Goaziou  writes:
> 
> > Hello,
> >
> > Suvayu Ali  writes:
> >
> >> Not sure why, but your -shell-escape option is being ignored.  Untill
> >> you can solve this properly, maybe you can put the LaTeX calls in a
> >> shell script and set that as your org-latex-pdf-process.
> >
> > I think the problem is that the OP uses `org-latex-to-pdf-process'
> > instead of `org-latex-pdf-process'.
> >
> >
> > Regards,
> 
> Hello Nicolas,
> 
> You are right, using org-latex-pdf-process solves the -shell-escape
> issue and C-c C-e l P produces the PDF without compaints.  Maybe the
> documentation [1] i got the code from should be updated?

Presently the manual is the most reliable source of information.
Followed by the Worg articles listed here:

  
  

Rest of the documentation is worked on at the moment.  Worg is a
community resource, so you can contribute too!  There was a recent (~1
month) post by Bastien outlining a procedure to mark deprecated
documentation on Worg.

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.

Re: [O] Source Code Syntax Highlighting in Beamer slides

[Alexander Baier]

Suvayu Ali  writes:

> Hi Alexander,
>
> On Sun, Apr 21, 2013 at 09:25:55PM +0200, Alexander Baier wrote:
>> 
>> I am trying to syntax-color the code in my source blocks that is
>> exported to LaTeX. As proposed in this thread [1] over a year ago I
>> followed this guide [2], but could not get the generated .tex file to
>> compile.
>
> [...chomp...chomp...chomp...]
>
>> Package ifplatform Warning: 
>> shell escape is disabled, so I can only detect \ifwindows.
>> 
>> )
>> \minted@bgbox=\box61
>> \minted@code=\write6
>> \@float@every@listing=\toks51
>> \c@listing=\count166
>> )
>> 
>> ! Package minted Error: You must invoke LaTeX with the -shell-escape flag.
>> 
>> See the minted package documentation for explanation.
>> Type  H   for immediate help.
>>  ...  
>>   
>> l.20 \usetheme
>>   {default}
>> Pass the -shell-escape flag to LaTeX. Refer to the minted.sty documentation 
>> for
>>  more information.
>> 
>> runsystem(which pygmentize && touch output.aex)...disabled (restricted).
>> 
>> 
>> ! Package minted Error: You must have `pygmentize' installed to use this 
>> packag
>> e.
>> 
>> See the minted package documentation for explanation.
>> Type  H   for immediate help.
>>  ...  
>>   
>> l.20 \usetheme
>>   {default}
>> Refer to the installation instructions in the minted documentation for more 
>> inf
>> ormation.
>
> [...chomp...chomp...chomp...]
>
>> runsystem(pygmentize -S default -f latex > output.pyg)...disabled 
>> (restricted).
>> 
>> 
>> 
>> ! LaTeX Error: File `output.pyg' not found.
>> 
>> Type X to quit or  to proceed,
>> or enter new name. (Default extension: pyg)
>
> Not sure why, but your -shell-escape option is being ignored.  Untill
> you can solve this properly, maybe you can put the LaTeX calls in a
> shell script and set that as your org-latex-pdf-process.
>
> Hope this helps,

Hello Suvayu,

Thank you for your answer.

Following your proposal:
---
(setq org-latex-to-pdf-process
  '("/home/delexi/orgtest/pdflatex-escaped.sh %o %f"
"/home/delexi/orgtest/pdflatex-escaped.sh %o %f"
"/home/delexi/orgtest/pdflatex-escaped.sh %o %f"))
---
Btw: Why is this a list of 3 identical tools/calls?

And pdflatex-escaped.sh:
---
#! /bin/bash
#
pdflatex -shell-escape -interaction nonstopmode -output-directory "$1" "$2"
---

Sadly, this leads to the same problem, complaining about -shell-escape.

When I only produce the .tex file (C-c C-e l b) and then manually
execute the before mentioned bash script on it, the PDF is generated without
any complaints.

Albeit there are not errors when creating the PDF file, the desired
syntax coloring does not take place and the source code simply appears
in black verbatim(?).

Do you have any more ideas?

Regards,

Alex

Re: [O] Source Code Syntax Highlighting in Beamer slides

[Alexander Baier]

Nicolas Goaziou  writes:

> Hello,
>
> Suvayu Ali  writes:
>
>> Not sure why, but your -shell-escape option is being ignored.  Untill
>> you can solve this properly, maybe you can put the LaTeX calls in a
>> shell script and set that as your org-latex-pdf-process.
>
> I think the problem is that the OP uses `org-latex-to-pdf-process'
> instead of `org-latex-pdf-process'.
>
>
> Regards,

Hello Nicolas,

You are right, using org-latex-pdf-process solves the -shell-escape
issue and C-c C-e l P produces the PDF without compaints.  Maybe the
documentation [1] i got the code from should be updated?


[1] http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3

Re: [O] Source Code Syntax Highlighting in Beamer slides

[Nicolas Goaziou]

Hello,

Suvayu Ali  writes:

> Not sure why, but your -shell-escape option is being ignored.  Untill
> you can solve this properly, maybe you can put the LaTeX calls in a
> shell script and set that as your org-latex-pdf-process.

I think the problem is that the OP uses `org-latex-to-pdf-process'
instead of `org-latex-pdf-process'.


Regards,

-- 
Nicolas Goaziou

Re: [O] Source Code Syntax Highlighting in Beamer slides

[Suvayu Ali]

Hi Alexander,

On Sun, Apr 21, 2013 at 09:25:55PM +0200, Alexander Baier wrote:
> 
> I am trying to syntax-color the code in my source blocks that is
> exported to LaTeX. As proposed in this thread [1] over a year ago I
> followed this guide [2], but could not get the generated .tex file to
> compile.

[...chomp...chomp...chomp...]

> Package ifplatform Warning: 
> shell escape is disabled, so I can only detect \ifwindows.
> 
> )
> \minted@bgbox=\box61
> \minted@code=\write6
> \@float@every@listing=\toks51
> \c@listing=\count166
> )
> 
> ! Package minted Error: You must invoke LaTeX with the -shell-escape flag.
> 
> See the minted package documentation for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.20 \usetheme
>   {default}
> Pass the -shell-escape flag to LaTeX. Refer to the minted.sty documentation 
> for
>  more information.
> 
> runsystem(which pygmentize && touch output.aex)...disabled (restricted).
> 
> 
> ! Package minted Error: You must have `pygmentize' installed to use this 
> packag
> e.
> 
> See the minted package documentation for explanation.
> Type  H   for immediate help.
>  ...  
>   
> l.20 \usetheme
>   {default}
> Refer to the installation instructions in the minted documentation for more 
> inf
> ormation.

[...chomp...chomp...chomp...]

> runsystem(pygmentize -S default -f latex > output.pyg)...disabled 
> (restricted).
> 
> 
> 
> ! LaTeX Error: File `output.pyg' not found.
> 
> Type X to quit or  to proceed,
> or enter new name. (Default extension: pyg)

Not sure why, but your -shell-escape option is being ignored.  Untill
you can solve this properly, maybe you can put the LaTeX calls in a
shell script and set that as your org-latex-pdf-process.

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.