Eric Schulte writes:
[...]
> I think both this and Torsten's original idea would both be nice
> options. Preferably the final solution would subsume either use case.
> Unfortunately either implementation would require a fairly significant
> amount of work on the inline source block system, wor
Eric Fraga writes:
> Eric Schulte writes:
>
>> Currently inline blocks like don't associate themselves with their
>> results, they are only expected to be evaluated on export, so the
>> functionality you suggest below would require first changing how results
>> are associated with inline code bl
Eric Schulte writes:
> Currently inline blocks like don't associate themselves with their
> results, they are only expected to be evaluated on export, so the
> functionality you suggest below would require first changing how results
> are associated with inline code blocks.
>
> Another option wou
Currently inline blocks like don't associate themselves with their
results, they are only expected to be evaluated on export, so the
functionality you suggest below would require first changing how results
are associated with inline code blocks.
Another option would be to hide everything but the b