Re: [Orgmode] Re: [babel] Environment around exported results

[Rainer M Krug]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24/09/10 11:28, Sébastien Vauban wrote:
> Hi Eric,
> 
> "Eric Schulte" wrote:
>> Sébastien Vauban <address@hidden> writes:
>>> "Eric Schulte" wrote:
>>>>> Would you mind creating an LaTeX environment around the =results= block,
>>>>> so that we could have the code colorized (via listings or Minted), and
>>>>> clearly distinguish the results, if we want so.
>>>>>
>>>>> Having an environment would allow one to use non-proportional font for
>>>>> the results, or a shadowed background, or...
>>>>
>>>> Would such an environment be in addition too or in place of wrapping
>>>> results in the example environment?
>>>
>>> I would think of something like this:
>>>
>>> \begin{orgresults}
>>> <... results block ...>
>>> \end{orgresults}
>>>
>>> so that one can customize the =orgresults= environment in LaTeX to get a
>>> colored background, another font, etc.
>>>
>>>> What would you suggest for tabular results?
>>>
>>> Nothing different for tables: just the same plain default environment
>>> around the results part.
>>>
>>>> One very nice property of the current setup is that it relies solely on
>>>> vanilla Org-mode for export features. If the example export of Org-mode
>>>> allowed some form of customization through a customizable div class or
>>>> latex environment would that be sufficient?
>>>
>>> The name of the environment could be in a variable, yes.
>>>
>>> But please note the above request can come out of a misunderstanding or
>>> poor knowledge of already existing parametrization of Org-Babel. Put me
>>> back on tracks if needed...
>>
>> I think you've made a good point for adding this functionality.
> 
> Thanks ;-)
> 
>> I'll put this on the Babel TODO stack, and reply to this email when we get
>> something implemented.
> 
> FYI, I think it such a thing should be on by default, but with a possibility
> to disable it, block per block (or subtree, or file, ...).
> 
> Something like a =:nowrapper= header argument?

Probably even one step further: being able to specify the environment to
be used in a header argument, so we would have three possible scenarios:

1) default (equals to :wrapper orgresults)   : using \begin{orgresults}
... \end{orgresult}
2) :nowrapper  : using no wrapper around the results block
3) :wrapper myEnvironment : using \begin{myEnvironment} ...
\end{myEnvironment}

This could possibly even extended to source blocks as well, enabling the
use of different formating for different source blocks?

Cheers,

Rainer

> 
> Many thanks in advance...
> 
> Best regards,
>   Seb
> 


- -- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa

Tel:        +33 - (0)9 53 10 27 44
Cell:       +27 - (0)8 39 47 90 42
Fax (SA):   +27 - (0)8 65 16 27 82
Fax (D) :   +49 - (0)3 21 21 25 22 44
Fax (FR):   +33 - (0)9 58 10 27 44
email:      address@hidden

Skype:      RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkydEZYACgkQoYgNqgF2egrXKgCfUK66v+huGysHoau6GRWy0wJr
UOAAmQGHseEUyUzI7pap5nB31SAnIN1T
=tkMG
-----END PGP SIGNATURE-----