Name of code pieces when exported to PDF

Name of code pieces when exported to PDF

[claude fuhrer]

Hello

To explain a small program, I've broken it down into small pieces. My
org file looks something like

# =========================================================================
#+NAME MainClass
#+BEGIN_SRC java :noweb tangle :tangle Test.java
public class Test
{
    <<secondBlock>>
    <<thirdBlock>>
}
#+END_SRC

some text

#+NAME secondBlock
#+BEGIN_SRC java :noweb tangle
     int a, b;
#+END_SRC

and then

#+NAME thirdBlock
#+BEGIN_SRC java :noweb tangle
     a = 17;
     b = a / 2;
#+END_SRC
# =========================================================================

Org-babel-tangle give me exactly what I want.

But, is it possible to have the "NAME" value displayed in the
lstlisting parameters when I export the org document as pdf ? I've
included the following lines in the beginning of my org file

#+LaTeX_HEADER:\lstset{language=Java,
#+LaTeX_HEADER:        numbers=left,
#+LaTeX_HEADER:        basicstyle=\footnotesize\ttfamily,
#+LaTeX_HEADER:        basicstyle=\ttfamily,
#+LaTeX_HEADER:        backgroundcolor=\color{LightYellow},
#+LaTeX_HEADER:        stringstyle=\color{blue},
#+LaTeX_HEADER:        frame=single,
#+LaTeX_HEADER:        columns=fullflexible,
#+LaTeX_HEADER:        numberstyle=\scriptsize\color{red},
#+LaTeX_HEADER:        commentstyle=\color{ForestGreen}}

The package listing provides a "title" or "caption" keyword, but I do
not know how to pass the "NAME" argument. Can you please help me or
give me a pointer ? Thank you in advance for your help.

Re: Name of code pieces when exported to PDF

[Nicolas Goaziou]

Hello,

claude fuhrer <claude@fuhrer.ch> writes:

> To explain a small program, I've broken it down into small pieces. My
> org file looks something like
>
> # =========================================================================
> #+NAME MainClass
>
> #+BEGIN_SRC java :noweb tangle :tangle Test.java
> public class Test
> {
>     <<secondBlock>>
>     <<thirdBlock>>
> }
> #+END_SRC

It should be

  #+name: MainClass
  #+begin_src ...

i.e, with dots and no blank line in-between.

Regards,

-- 
Nicolas Goaziou

Re: Name of code pieces when exported to PDF

[claude fuhrer]

Hi Nicolas


On 26/09/16 17:34, Nicolas Goaziou wrote:
> Hello,
>
> claude fuhrer <claude@fuhrer.ch> writes:
>
>> [...]
> It should be
>
>    #+name: MainClass
>    #+begin_src ...
>
> i.e, with dots and no blank line in-between.

Thank you for your quick answer, but I do not really understand how to 
use it. I've corrected the syntax as you mentioned and shows what is the 
generated latex code. The export process gives then:



\lstset{language=java,label=secondBlock,caption= ,captionpos=b,numbers=none}
\begin{lstlisting}
.....
\end{lstlisting}

But I wanted to have the "caption" filled with the same value as the 
label. Is it possible ?

Thank you once again for your help.

regards
claude


>
> Regards,
>

Re: Name of code pieces when exported to PDF

[Sebastian Christ]

On 2016-09-26 18:48, claude fuhrer <claude@fuhrer.ch> wrote:
 > \lstset{language=java,label=secondBlock,caption= ,captionpos=b,numbers=none}
 > \begin{lstlisting}
 > .....
 > \end{lstlisting}
 > 
 > But I wanted to have the "caption" filled with the same value as the
 > label. Is it possible ?
 > 
Yes, use caption!

#+caption: MainClass
#+name: MainClass
#+begin_src ...

Regards,
Sebastian 
-- 
Sebastian (Rudolfo) Christ
http://rudolfochrist.github.io
GPG Fingerprint: 306D 8FD3 DFB6 4E44 5061
                 CE71 6407 D6F8 2AC5 55DD

Re: Name of code pieces when exported to PDF

[Nick Dokos]

Sebastian Christ <rudolfo.christ@gmail.com> writes:

> On 2016-09-26 18:48, claude fuhrer <claude@fuhrer.ch> wrote:
>  > \lstset{language=java,label=secondBlock,caption= ,captionpos=b,numbers=none}
>  > \begin{lstlisting}
>  > .....
>  > \end{lstlisting}
>  > 
>  > But I wanted to have the "caption" filled with the same value as the
>  > label. Is it possible ?
>  > 
> Yes, use caption!
>
> #+caption: MainClass
> #+name: MainClass
>
> #+begin_src ...
>

That seems indeed to be necessary (at least in a few experiments that
I've run), but it's less than ideal (duplication of information).

I was under the impression that #+CAPTION is deprecated and #+NAME is
to be used in its place going forward. If that's the case, then the
listings problem needs fixing.  If not, can somebody summarize the
actual situation?

Thanks!
-- 
Nick

Name of code pieces when exported to PDF

[John Kitchin]

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

It is #+label that is deprecated in favor of #+name.

On Monday, September 26, 2016, Nick Dokos <ndokos@gmail.com
<javascript:_e(%7B%7D,'cvml','ndokos@gmail.com');>> wrote:

> Sebastian Christ <rudolfo.christ@gmail.com> writes:
>
> > On 2016-09-26 18:48, claude fuhrer <claude@fuhrer.ch> wrote:
> >  > \lstset{language=java,label=secondBlock,caption=
> ,captionpos=b,numbers=none}
> >  > \begin{lstlisting}
> >  > .....
> >  > \end{lstlisting}
> >  >
> >  > But I wanted to have the "caption" filled with the same value as the
> >  > label. Is it possible ?
> >  >
> > Yes, use caption!
> >
> > #+caption: MainClass
> > #+name: MainClass
> >
> > #+begin_src ...
> >
>
> That seems indeed to be necessary (at least in a few experiments that
> I've run), but it's less than ideal (duplication of information).
>
> I was under the impression that #+CAPTION is deprecated and #+NAME is
> to be used in its place going forward. If that's the case, then the
> listings problem needs fixing.  If not, can somebody summarize the
> actual situation?
>
> Thanks!
> --
> Nick
>
>
>

-- 
John

-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

[-- Attachment #2: Type: text/html, Size: 1901 bytes --]

Re: Name of code pieces when exported to PDF

[Nick Dokos]

John Kitchin <jkitchin@andrew.cmu.edu> writes:

> It is #+label that is deprecated in favor of #+name. 
>

Ah, thanks!

> On Monday, September 26, 2016, Nick Dokos <ndokos@gmail.com> wrote:
>
>     ...   
>     I was under the impression that #+CAPTION is deprecated and #+NAME is
>     to be used in its place going forward. If that's the case, then the
>     listings problem needs fixing.  If not, can somebody summarize the
>     actual situation?
>    

-- 
Nick

Re: Name of code pieces when exported to PDF

[Sebastian Christ]

On 2016-09-26 17:32, Nick Dokos <ndokos@gmail.com> wrote:
 >> #+caption: MainClass
 >> #+name: MainClass
 >> 
 >> #+begin_src ...
 > That seems indeed to be necessary (at least in a few experiments that
 > I've run), but it's less than ideal (duplication of information).

In this peculiar case, yes. But, at least for me, I use each for a
different purpose that doesn't duplicate the information. I'm using
org-ref for references and most of the time a more meaningful
caption. For example:

#+caption: A class with a main method
#+name: lst-main
#+begin_src java

Regards,

Sebastian

-- 
Sebastian (Rudolfo) Christ
http://rudolfochrist.github.io
GPG Fingerprint: 306D 8FD3 DFB6 4E44 5061
                 CE71 6407 D6F8 2AC5 55DD