Re: (almost a patch) Receiving more output from a Common Lisp evaluation in Org buffer

2020-07-06 Thread akater
stardiviner writes: > I have some considering. Multi-block return might will cause other options > hard > to handle the result block. For example ~:cache~, ~:results replace~, and use > result > as source block input data. WDYT? Probably. I'm not a user of either :cache or :results replace

Re: (almost a patch) Receiving more output from a Common Lisp evaluation in Org buffer

2020-05-24 Thread stardiviner
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 akater writes: > * Summary > I have a patch that allows to put trace output and error output into > corresponding Org buffer. Current behaviour with outputs being splitted > so that they go to different buffers (Org buffer, REPL), is arbitrary >

Re: (almost a patch) Receiving more output from a Common Lisp evaluation in Org buffer

2020-05-24 Thread Bastien
Hi, akater writes: > I have a patch that allows to put trace output and error output into > corresponding Org buffer. Can you share the patch (as an attachment)? Does it add a functionality just for one ob-* library or for babel evaluation in general? > Current behaviour with outputs being

(almost a patch) Receiving more output from a Common Lisp evaluation in Org buffer

2020-04-08 Thread akater
* Summary I have a patch that allows to put trace output and error output into corresponding Org buffer. Current behaviour with outputs being splitted so that they go to different buffers (Org buffer, REPL), is arbitrary and inconvenient. The patch ensures backwards compatibility. I thus believe