Nice python listings colors, or solution to beamer + minted brokenness?

Nice python listings colors, or solution to beamer + minted brokenness?

[Christopher Allan Webber]

Hello all,

I currently am trying to export something vaguely like this for a
presentation in beamer:

#+BEGIN_SRC python :exports code
class ReferenceDeskPanel(bpy.types.Panel):
    bl_label = 'Reference Desk'
    bl_space_type = 'VIEW_3D'
    bl_region_type = 'TOOLS'

    def draw(self, context):
        layout = self.layout

        row = layout.row()
        row.prop(
            context.scene, 'refdesk_search',
            text="", icon='VIEWZOOM')

        search_string = context.scene.get('refdesk_search')
#+END_SRC

I've tried using listings with:

#+begin_LaTeX
  \definecolor{keywords}{RGB}{255,0,90}
  \definecolor{comments}{RGB}{60,179,113}
  
  \lstset{
    language=\Python,
    keywordstyle=\color{keywords},
    commentstyle=\color{comments}emph,
    procnamestyle=\color{blue}\textbf,
    emphstyle=\color{black}\bfseries, 
    }
#+end_LaTeX

in my document but I can't figure out how to get the class name
(ReferenceDeskPanel) to be highlighted in any form.  I've read through
the listings manual but I can't find any reference on how to do this.

I also tried using minted, but I'm running into the problem discussed in
this thread:

http://article.gmane.org/gmane.emacs.orgmode/32147/match=minted

I'm at wit's end... I just want to figure out how to syntax highlight my
whole python snippet!  Any examples of good color sets in listings to
use would be *greatly* appreciated!  Or a solution to that minted +
beamer problem!  Either one!

Super, ultra thanks in advance,
 - cwebb

-- 
𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻

Re: Nice python listings colors, or solution to beamer + minted brokenness?

[Chris Malone]

[-- Attachment #1.1: Type: text/plain, Size: 2225 bytes --]

Hi Chris,

I doubt this will fix the problem (it is more of a curiosity), but why in
your =lstset= do you have the language as "\Python" instead of "Python"?

Chris


On Sun, Feb 13, 2011 at 7:35 PM, Christopher Allan Webber <
cwebber@dustycloud.org> wrote:

> Hello all,
>
> I currently am trying to export something vaguely like this for a
> presentation in beamer:
>
> #+BEGIN_SRC python :exports code
> class ReferenceDeskPanel(bpy.types.Panel):
>    bl_label = 'Reference Desk'
>    bl_space_type = 'VIEW_3D'
>    bl_region_type = 'TOOLS'
>
>    def draw(self, context):
>        layout = self.layout
>
>        row = layout.row()
>        row.prop(
>            context.scene, 'refdesk_search',
>            text="", icon='VIEWZOOM')
>
>        search_string = context.scene.get('refdesk_search')
> #+END_SRC
>
> I've tried using listings with:
>
> #+begin_LaTeX
>  \definecolor{keywords}{RGB}{255,0,90}
>  \definecolor{comments}{RGB}{60,179,113}
>
>  \lstset{
>    language=\Python,
>    keywordstyle=\color{keywords},
>    commentstyle=\color{comments}emph,
>    procnamestyle=\color{blue}\textbf,
>    emphstyle=\color{black}\bfseries,
>    }
> #+end_LaTeX
>
> in my document but I can't figure out how to get the class name
> (ReferenceDeskPanel) to be highlighted in any form.  I've read through
> the listings manual but I can't find any reference on how to do this.
>
> I also tried using minted, but I'm running into the problem discussed in
> this thread:
>
> http://article.gmane.org/gmane.emacs.orgmode/32147/match=minted
>
> I'm at wit's end... I just want to figure out how to syntax highlight my
> whole python snippet!  Any examples of good color sets in listings to
> use would be *greatly* appreciated!  Or a solution to that minted +
> beamer problem!  Either one!
>
> Super, ultra thanks in advance,
>  - cwebb
>
> --
> 𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

[-- Attachment #1.2: Type: text/html, Size: 3065 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Nice python listings colors, or solution to beamer + minted brokenness?

[Chris Malone]

[-- Attachment #1.1: Type: text/plain, Size: 3004 bytes --]

Also, it's not an elegant or automated solution, but check out Section 2.8:
Emphasize Identifiers in the listings manual.  You could basically add
something like

emph={ReferenceDeskPanel}, emphstyle=\color{blue}

to your =lstset= to get that particular class to have a blue font.  You
could add such a line for /every/ class you have by putting in the optional
<class number> argument as described in the manual.  I don't know how one
could do this for every word that follows the Python =class= directive, as
the =lstset= /key-value/ setup doesn't allow for such things...

HTH,

Chris

On Sun, Feb 13, 2011 at 8:46 PM, Chris Malone <chris.m.malone@gmail.com>wrote:

>
> Hi Chris,
>
> I doubt this will fix the problem (it is more of a curiosity), but why in
> your =lstset= do you have the language as "\Python" instead of "Python"?
>
> Chris
>
>
>
> On Sun, Feb 13, 2011 at 7:35 PM, Christopher Allan Webber <
> cwebber@dustycloud.org> wrote:
>
>> Hello all,
>>
>> I currently am trying to export something vaguely like this for a
>> presentation in beamer:
>>
>> #+BEGIN_SRC python :exports code
>> class ReferenceDeskPanel(bpy.types.Panel):
>>    bl_label = 'Reference Desk'
>>    bl_space_type = 'VIEW_3D'
>>    bl_region_type = 'TOOLS'
>>
>>    def draw(self, context):
>>        layout = self.layout
>>
>>        row = layout.row()
>>        row.prop(
>>            context.scene, 'refdesk_search',
>>            text="", icon='VIEWZOOM')
>>
>>        search_string = context.scene.get('refdesk_search')
>> #+END_SRC
>>
>> I've tried using listings with:
>>
>> #+begin_LaTeX
>>  \definecolor{keywords}{RGB}{255,0,90}
>>  \definecolor{comments}{RGB}{60,179,113}
>>
>>  \lstset{
>>    language=\Python,
>>    keywordstyle=\color{keywords},
>>    commentstyle=\color{comments}emph,
>>    procnamestyle=\color{blue}\textbf,
>>    emphstyle=\color{black}\bfseries,
>>    }
>> #+end_LaTeX
>>
>> in my document but I can't figure out how to get the class name
>> (ReferenceDeskPanel) to be highlighted in any form.  I've read through
>> the listings manual but I can't find any reference on how to do this.
>>
>> I also tried using minted, but I'm running into the problem discussed in
>> this thread:
>>
>> http://article.gmane.org/gmane.emacs.orgmode/32147/match=minted
>>
>> I'm at wit's end... I just want to figure out how to syntax highlight my
>> whole python snippet!  Any examples of good color sets in listings to
>> use would be *greatly* appreciated!  Or a solution to that minted +
>> beamer problem!  Either one!
>>
>> Super, ultra thanks in advance,
>>  - cwebb
>>
>> --
>> 𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
>
>

[-- Attachment #1.2: Type: text/html, Size: 4157 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Nice python listings colors, or solution to beamer + minted brokenness?

[Christopher Allan Webber]

Hi Chris,

That'll work well enough for now I think.  Thanks much for the response!

Chris Malone <chris.m.malone@gmail.com> writes:

> Also, it's not an elegant or automated solution, but check out Section
> 2.8: Emphasize Identifiers in the listings manual.? You could
> basically add something like
>
> emph={ReferenceDeskPanel}, emphstyle=\color{blue}
>
> to your =lstset= to get that particular class to have a blue font.?
> You could add such a line for /every/ class you have by putting in the
> optional <class number> argument as described in the manual.? I don't
> know how one could do this for every word that follows the Python
> =class= directive, as the =lstset= /key-value/ setup doesn't allow for
> such things...
>
> HTH,
>
> Chris
>
> On Sun, Feb 13, 2011 at 8:46 PM, Chris Malone <chris.m.malone@gmail.com> wrote:
>
>     Hi Chris,
>    
>     I doubt this will fix the problem (it is more of a curiosity), but why in your =lstset= do you have the language as "\Python" instead of "Python"?
>    
>     Chris
>
>     On Sun, Feb 13, 2011 at 7:35 PM, Christopher Allan Webber <cwebber@dustycloud.org> wrote:
>    
>         Hello all,
>        
>         I currently am trying to export something vaguely like this for a
>         presentation in beamer:
>
> #+BEGIN_SRC python :exports code<br>
> class ReferenceDeskPanel(bpy.types.Panel):<br>
>  . .bl_label = &#39;Reference Desk&#39;<br>
>  . .bl_space_type = &#39;VIEW_3D&#39;<br>
>  . .bl_region_type = &#39;TOOLS&#39;<br>
> <br>
>  . .def draw(self, context):<br>
>  . . . .layout = self.layout<br>
> <br>
>  . . . .row = layout.row()<br>
>  . . . .row.prop(<br>
>  . . . . . .context.scene, &#39;refdesk_search&#39;,<br>
>  . . . . . .text=&quot;&quot;, icon=&#39;VIEWZOOM&#39;)<br>
> <br>
>  . . . .search_string = context.scene.get(&#39;refdesk_search&#39;)<br>
> #+END_SRC<br>
> I've tried using listings with:
>
> #+begin_LaTeX<br>
>  .\definecolor{keywords}{RGB}{255,0,90}<br>
>  .\definecolor{comments}{RGB}{60,179,113}<br>
> <br>
>  .\lstset{<br>
>  . .language=\Python,<br>
>  . .keywordstyle=\color{keywords},<br>
>  . .commentstyle=\color{comments}emph,<br>
>  . .procnamestyle=\color{blue}\textbf,<br>
>  . .emphstyle=\color{black}\bfseries,<br>
>  . .}<br>
> #+end_LaTeX<br>
> in my document but I can't figure out how to get the class name
> (ReferenceDeskPanel) to be highlighted in any form. ?I've read through
> the listings manual but I can't find any reference on how to do this.
>
> I also tried using minted, but I'm running into the problem discussed in
> this thread:
>
> http://article.gmane.org/gmane.emacs.orgmode/32147/match=minted
>
> I'm at wit's end... I just want to figure out how to syntax highlight my
> whole python snippet! ?Any examples of good color sets in listings to
> use would be *greatly* appreciated! ?Or a solution to that minted +
> beamer problem! ?Either one!
>
> Super, ultra thanks in advance,
> ?- cwebb
>
> --
> ??????????? ????? ??????
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

-- 
𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻

Re: Nice python listings colors, or solution to beamer + minted brokenness?

[Dan Davison]

Christopher Allan Webber <cwebber@dustycloud.org> writes:

> Hello all,
>
> I currently am trying to export something vaguely like this for a
> presentation in beamer:
>
> #+BEGIN_SRC python :exports code
> class ReferenceDeskPanel(bpy.types.Panel):
>     bl_label = 'Reference Desk'
>     bl_space_type = 'VIEW_3D'
>     bl_region_type = 'TOOLS'
>
>     def draw(self, context):
>         layout = self.layout
>
>         row = layout.row()
>         row.prop(
>             context.scene, 'refdesk_search',
>             text="", icon='VIEWZOOM')
>
>         search_string = context.scene.get('refdesk_search')
> #+END_SRC
>
> I've tried using listings with:
>
> #+begin_LaTeX
>   \definecolor{keywords}{RGB}{255,0,90}
>   \definecolor{comments}{RGB}{60,179,113}
>   
>   \lstset{
>     language=\Python,
>     keywordstyle=\color{keywords},
>     commentstyle=\color{comments}emph,
>     procnamestyle=\color{blue}\textbf,
>     emphstyle=\color{black}\bfseries, 
>     }
> #+end_LaTeX
>
> in my document but I can't figure out how to get the class name
> (ReferenceDeskPanel) to be highlighted in any form.  I've read through
> the listings manual but I can't find any reference on how to do this.
>
> I also tried using minted, but I'm running into the problem discussed in
> this thread:
>
> http://article.gmane.org/gmane.emacs.orgmode/32147/match=minted

Hi Christopher,

I believe I have just fixed the problem with minted and beamer. Please
pull latex org from git and restart emacs, or

(setq org-beamer-fragile-re "^[ \t]*\\\\begin{\\(verbatim\\|lstlisting\\|minted\\)}")

Personally I think that minted will be preferable to listings for your
application.

Dan

>
> I'm at wit's end... I just want to figure out how to syntax highlight my
> whole python snippet!  Any examples of good color sets in listings to
> use would be *greatly* appreciated!  Or a solution to that minted +
> beamer problem!  Either one!
>
> Super, ultra thanks in advance,
>  - cwebb

Re: Nice python listings colors, or solution to beamer + minted brokenness?

[Christopher Allan Webber]

Dan Davison <dandavison7@gmail.com> writes:

> Hi Christopher,
>
> I believe I have just fixed the problem with minted and beamer. Please
> pull latex org from git and restart emacs, or
>
> (setq org-beamer-fragile-re "^[ \t]*\\\\begin{\\(verbatim\\|lstlisting\\|minted\\)}")
>
> Personally I think that minted will be preferable to listings for your
> application.
>
> Dan

Dan:

It works!  That looks *fantastic.*  Thank you *so* much! :D :D :D

 - cwebb

-- 
𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻

Re: Nice python listings colors, or solution to beamer + minted brokenness?

[Dan Davison]

Christopher Allan Webber <cwebber@dustycloud.org> writes:

> Dan Davison <dandavison7@gmail.com> writes:
>
>> Hi Christopher,
>>
>> I believe I have just fixed the problem with minted and beamer. Please
>> pull latex org from git and restart emacs, or
           ^^^

Oops, I meant to write "latest" org. I.e. just pull as normal.

>>
>> (setq org-beamer-fragile-re "^[ \t]*\\\\begin{\\(verbatim\\|lstlisting\\|minted\\)}")
>>
>> Personally I think that minted will be preferable to listings for your
>> application.
>>
>> Dan
>
> Dan:
>
> It works!  That looks *fantastic.* 

Great.

If you want to play around with styles, you can use a line like

#+latex_header: \usemintedstyle{tango}

To see all the available styles, use the command

pygmentize -L styles

(my output is below)

Also, if you'd like to experiment with the different options for
the \begin{minted} environment, and if you're comfortable switching
between git branches, then try the branch "minted" of the main org git
repo, and look at the variable `org-export-latex-minted-options'. For
example

(setq org-export-latex-minted-options '(("frame" "lines")))

puts a frame around the src block. Of course, see minted.pdf for the
options.

Dan

$ pygmentize -L styles
Pygments version 1.4, (c) 2006-2008 by Georg Brandl.

Styles:
~~~~~~~
* monokai:
    This style mimics the Monokai color scheme.
* manni:
    A colorful style, inspired by the terminal highlighting style.
* perldoc:
    Style similar to the style used in the perldoc code blocks.
* borland:
    Style similar to the style used in the borland IDEs.
* colorful:
    A colorful style, inspired by CodeRay.
* default:
    The default style (inspired by Emacs 22).
* murphy:
    Murphy's style from CodeRay.
* vs:
    
* trac:
    Port of the default trac highlighter design.
* tango:
    The Crunchy default Style inspired from the color palette from the Tango Icon Theme Guidelines.
* fruity:
    Pygments version of the "native" vim theme.
* autumn:
    A colorful style, inspired by the terminal highlighting style.
* bw:
    
* emacs:
    The default style (inspired by Emacs 22).
* vim:
    Styles somewhat like vim 7.0
* pastie:
    Style similar to the pastie default style.
* friendly:
    A modern style based on the VIM pyte theme.
* native:
    Pygments version of the "native" vim theme.


> Thank you *so* much! :D :D :D


>
>  - cwebb

Re: Nice python listings colors, or solution to beamer + minted brokenness?

[Christopher Allan Webber]

[-- Attachment #1: Type: text/plain, Size: 252 bytes --]

Dan, all this information is super helpful.  Thanks!  My presentation is
going to look great now, I think!

I really appreciate your help!
 - cwebb

-- 
𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Re: Nice python listings colors, or solution to beamer + minted brokenness?

[Chris Malone]

[-- Attachment #1.1: Type: text/plain, Size: 3566 bytes --]

Hi Chris

Just for completeness - and because I had little previous experience with
using =org-babel= stuff - I attempted to write a small =sh= source block
that parses the current =org-mode= file and builds an appropriate "emph"
entry in the listings =lstset=:

==========================================================================================
#+startup:
beamer

#+LaTeX_CLASS:
beamer

#+BEAMER_HEADER_EXTRA:
\usetheme{Madrid}\usecolortheme{default}

#+source: parse-classes


#+begin_src sh :var fileName=(buffer-file-name) :exports none :results
output latex
  for class in `sed -n 's/.*class \([a-zA-Z0-9_]*\)(.*):/\1/p' $fileName`;
do

str="$str,$class"


done

  cat
<<EOF


\\definecolor{keywords}{RGB}{255,0,90}


\\definecolor{comments}{RGB}{60,179,113}


\\lstset{


language=Python,


keywordstyle=\\color{keywords},


commentstyle=\\color{comments},


procnamestyle=\\color{blue}\bfseries,


emph={${str:1}},


emphstyle=\\color{blue}\bfseries


}


EOF

#+end_src



*
test

** Panels in the UI (part
1)


Scripting the UI is pretty much the same as scripting the
operator,
but it goes to a separate
location..


*** Panel operator
:B_block:

:PROPERTIES:

   :BEAMER_env:
block


:END:



#+BEGIN_SRC python :exports
code
class
ReferenceDeskPanel(bpy.types.Panel):


pass

#+END_SRC



#+BEGIN_SRC python :exports
code
class
ReferenceDeskPanel23(bpy.types.Panel):


pass

#+END_SRC
==========================================================================================

There are two somewhat inconvenient issues with this approach:

- One has to evaluate the =parse-classes= source block before export, via a
=C-c C-c=.  This allows the results to be added directly to buffer as LaTeX
source code.  This was the only way I could figure out how to get it to work
- maybe someone else has a clever work around?

Part of the problem is that by the point that the code would be evaluated,
you are already within the body of the LaTeX document.  It would be nice if
there were a =#+begin_latex_document= command which would allow for anything
before this command to be in the document's preamble, and anything
afterwords to follow the LaTeX command =\begin{document}=.  Maybe this is a
feature request?

- One cannot use listings ability to use /class numbers/ to mark particular
emphasis because they get interpreted by =org-mode= as footnotes.  For
example, say you wanted all the /class/ emphasis words to be blue, but you
wanted all /def/ emphasis words to be red.  In LaTeX one could write

#+begin_latex
  \lstset{
    emph={def}, emphstyle=\color{red},
    emph={[2]class}, emphstyle=\color{blue}
#+end_latex

This can't be done with the above =parse-classes= code.

Anyway, it's a bit long-winded and probably moot seeing as how you decided
to use =minted=, but I thought I'd give it a shot.

Chris
On Mon, Feb 14, 2011 at 11:12 AM, Christopher Allan Webber <
cwebber@dustycloud.org> wrote:

> Dan, all this information is super helpful.  Thanks!  My presentation is
> going to look great now, I think!
>
> I really appreciate your help!
>  - cwebb
>
> --
> 𝓒𝓱𝓻𝓲𝓼𝓽𝓸𝓹𝓱𝓮𝓻 𝓐𝓵𝓵𝓪𝓷 𝓦𝓮𝓫𝓫𝓮𝓻
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>

[-- Attachment #1.2: Type: text/html, Size: 10214 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode