Re: [O] Feature Request: allow export yes/no for blocks that are valid babel inputs

[Berry, Charles]

AFAICS, the functionality you seek already exists, although it is not heavily 
advertised.

`C-c C-x t' will insert an inline task. Within such a `task' you can put text, 
tables, src blocks and other objects.

Setting option `inline:nil' will prevent export, but leave the content visible 
to src blocks etc.

Alternatively, you can tag inlinetasks as with headlines to control their 
export.

Browse the commentary in org-inlinetask.el for more details.

HTH,

Chuck


> On Mar 23, 2019, at 2:20 PM, Carlos Pita <address@hidden> wrote:
> 
> Hi all,
> 
> when using lists, tables and example blocks as inputs to babel src
> blocks sometimes the inputs are just... inputs. There is some
> inconsistency in the fact that src blocks can be selectively exported
> but not their inputs. Commenting these inputs out makes them invisible
> to the block referencing them (apparently this method worked a time
> ago but it's not working now). OTOH using the noexport tag introduces
> spurious sections that interrupt the flow of the document and might be
> hard to close afterwards (similar to the boilerplate introduced by
> beamer blocks).
> 
> What do you think of adding an :export yes/no parameter to these
> blocks? Or to blocks in general.
> 
> Best regards
> --
> Carlos
> 
>