• State "PROPOSED" from "" 2010-03-03 Wed 14:04 I just noticed the following link types in the org manual

shell:ls *.org                            A shell command
elisp:org-agenda                          Interactive Elisp command
elisp:(find-file-other-frame "Elisp.org") Elisp form to evaluate

The above can be placed within the standard construct:

[[link][description]]

I wonder whether we had that sufficiently in mind when we designed our in-line blocks? Some possibilities that come to mind are:

The above suggests that babel could extend org by supporting

[[ruby: 2+2]] and [[ruby: 2+2][description]]

etc.

And perhaps header args in {} rather than []

[[ruby{:session}]] and [[ruby{:session}: 2+2][description]]

If we needed to differentiate the babel handler from the org handler then we could use

[[src_ruby: 2+2]]

although I think I would like to keep the syntax identical, using variables to decide who handles what, so that it is invisible to the user.