Timeline for org export with interleaved output
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 26, 2020 at 15:26 | vote | accept | Sibi | ||
| Nov 26, 2020 at 15:11 | comment | added | NickD | As you wish :-) | |
| Nov 26, 2020 at 15:10 | answer | added | NickD | timeline score: 2 | |
| Nov 26, 2020 at 15:00 | comment | added | Sibi | @NickD Thanks! Can you add that as an answer ? I could delete the question, but I feel others who are beginning to explore Org babel (like me!) might get the same question. | |
| Nov 26, 2020 at 14:55 | comment | added | NickD | There is nothing like that: Org babel evaluates the source block by storing all the commands in a temp file, runs the file using the appropriate language interpreter, collects the output, does minor munging to it and writes it out as the results block. What you are asking for is fundamentally incompatible with the babel model. | |
| Nov 26, 2020 at 14:48 | comment | added | Sibi |
@NickD Yeah, that would be one way. I was hoping that there would be some tweaks to the source block which would allow interleaved output. Something like: :exports both-interleaved :-) But I guess it's not present.
|
|
| Nov 26, 2020 at 14:32 | comment | added | NickD | One way is to have multiple source blocks, one for each command. | |
| Nov 26, 2020 at 14:31 | history | edited | NickD | CC BY-SA 4.0 |
deleted 8 characters in body
|
| Nov 26, 2020 at 7:09 | history | asked | Sibi | CC BY-SA 4.0 |