Re: layout org-babel menu WAS: About org-babel menu

[Eric Schulte <eric.schulte@gmx.com>]

Rainer M Krug <r.m.krug@gmail.com> writes:

> On Wed 11 Apr 2012 10:11:01 CEST, Bastien wrote:
>> Hi Rainer,
>>
>> Rainer M Krug <r.m.krug@gmail.com> writes:
>>
>>> Thanks Bastien - here is my suggestion and if no objections are raised, I would suggest to
>>> implement it:
>>
>> I don't understand the "..." parts in your example.
>
> e.g. "... all languages supported" means a menu entry should be added
> for each language.
>
> Similar in the "header" menu, all headers should be filled in, although
> I would leave the header section out at the moment.
>
> Hope this helps,
>

There are still ambiguous parts, IMO the following should be fully
explicitly expanded

>  + header arguments
> |  |
> |  + general
> |  |   + export ...
> |  |   + ...

> |  + Show
> |  |    + Header arguments for code block
> |  |    + Header arguments for all code block in buffer
> |  |    + ...

>  + help
> |  |
> |  + Link to info help on header arguments
> |  + Link to info help on how to enable languages
> |  + URL to language specific help on worg
> |  + ...
> |  + ...

Additionally there are more evaluation functions which are not included
in the menu, please ensure that every user-visible function shown by
running `org-babel-describe-bindings' in an Org-mode buffer is included.

The other parts can be expanded using the given variables.

>  + Library of BABEL
> |  |
> |  + ... functions in the library - is this feasible?

Should only be displayed if `org-babel-library-of-babel' is non-nil, and
it's contents may be used to expand the menu option.

> |  + Language specific
> |  |   + R
> |  |   |    + file ...
> |  |   |    + ...
> |  |   |    + ...
> |  |   + Python
> |  |   |    + ...
> |  |   |    + ...
> |  |   |
> |  |   + ...

These may be expanded using the language specific header argument
variables which my latest un-applied patch introduces.  These have names
like `org-babel-header-args:lang'.

Best,

>
> Rainer
>
>
>>
>>> I think that is it for the moment - the header arguments section, specifically the language
>>> specific one, should possibly be left out as Eric is working on the autocomplete feature, which
>>> could possibly be called from the menu as well when implemented?
>>
>> Eric's take.
>>
>> Thanks!
>>
>
>
>
> --
> Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
> Biology, UCT), Dipl. Phys. (Germany)
>
> Centre of Excellence for Invasion Biology
> Stellenbosch University
> South Africa
>
> Tel :       +33 - (0)9 53 10 27 44
> Cell:       +33 - (0)6 85 62 59 98
> Fax :       +33 - (0)9 58 10 27 44
>
> Fax (D):    +49 - (0)3 21 21 25 22 44
>
> email:      Rainer@krugs.de
>
> Skype:      RMkrug

-- 
Eric Schulte
http://cs.unm.edu/~eschulte/