Only needs to be in the exported document, and doesn't necessarily need to
render that way within org. However, I'd like to avoid having to choose the
export form with custom markup in the org document. I often have documents,
or parts of docs, that are exported to both HTML and latex.
The equival
> On Feb 8, 2020, at 2:13 AM, Fraga, Eric wrote:
>
> On Friday, 7 Feb 2020 at 17:59, Steve Downey wrote:
>> I have a need to lay out source blocks side by side, in order to present
>> before and after changes to the source. If I could embed a block in a
>> table, that would do it.
>
> Do you
On Friday, 7 Feb 2020 at 17:59, Steve Downey wrote:
> I have a need to lay out source blocks side by side, in order to present
> before and after changes to the source. If I could embed a block in a
> table, that would do it.
Do you need this layout in org file itself or only in an exported
docum
I have a need to lay out source blocks side by side, in order to present
before and after changes to the source. If I could embed a block in a
table, that would do it.
Is there another obvious way that I'm missing?
Hilight etc is important, but also actually compiling the code to maintain
correct
