Rainer M Krug <[email protected]> writes:
> In a document, I have several source blocks with "real" code (i.e. bash and R
> in this case) Now I
> have one block, which is not really source code, but which is "kind of"
> source code, in my case a
> definition of a projection for a GIS project. Now I would like to have this
> definition of the
> projection displayed in the exported document as the other source blocks, If
> I put it into an
> EXAMPLE block, it is exported to LaTeX as verbatin and not listing, and all
> customisations ai have
> for listings (smaller font, grey background, ...) do *not* apply to the
> EXAMPLE block, but woyuld
> to a "fundamental" source block. So the EXAMPLE block is in this case not
> equivalent to the
> fundamental source block.
>
> Hope this clarifies the difference,
Yes, thanks.
Since you use "listings" package, can't you define a new language (i.e.
with \lstdefinelanguage{pseudocode}) and then use "#+begin_src
pseudocode" block?
Regards,
--
Nicolas Goaziou
