On 2019-10-11 at 00:13 +02, Tim Cross wrote...
> My concern with this suggestion is that I think it my result in
> 'surprising' or unexpected results for users.
I hope nobody would be surprised if they C-u C-u C-c C-c'd ! :) Just as they
shouldn't be surprised if the :cache is ignored, if run
My concern with this suggestion is that I think it my result in
'surprising' or unexpected results for users. I use tangle a fair
bit, but evaluate source blocks far less. I use :tangle no to mean do
not tangle - no if, but or maybe - if the block has :tangle no, then I
don not expect the block
> On Oct 10, 2019, at 10:21 AM, Charles Berry wrote:
>
>>
>> This could work in theory, but doesn't for bash on my system. And (I think)
>> with this method tables of output are not then injected back into the Org
>> buffer that can be exported as part of the document.
>
Of course!
>
>
> On Oct 10, 2019, at 9:43 AM, Ken Mankoff wrote:
>
> Hi Charles,
>
> On 2019-10-10 at 18:22 +02, Berry, Charles wrote...
>> If the language mode you use supports of evaluation of the src edit
>> buffer (e.g. ESS[R], Python), you can issue
>>
>> C-c C-v v C-c C-b
>>
>> for ESS[R] or
>>
Hi Charles,
On 2019-10-10 at 18:22 +02, Berry, Charles wrote...
> If the language mode you use supports of evaluation of the src edit
> buffer (e.g. ESS[R], Python), you can issue
>
> C-c C-v v C-c C-b
>
> for ESS[R] or
>
> C-c C-v v C-c C-c
>
> for Python (I think)
>
> The commands will expand
> On Oct 9, 2019, at 11:04 PM, Ken Mankoff wrote:
>
> Hello,
>
> I think that even when ":eval no" is set, eval should happen if the user
> explicitly requests it.
If the language mode you use supports of evaluation of the src edit buffer
(e.g. ESS[R], Python), you can issue
C-c C-v v
Hello,
I think that even when ":eval no" is set, eval should happen if the user
explicitly requests it.
The use case is that I have code that takes an unreasonable amount of compute
time to run it in Emacs (e.g. a full day of compute time). I think even with
:async this type of code should be
I guess this is not easily possible without some advice. When you run
org-babel-execute-buffer the cursor moves into each block, so you need to
save the point before you run it, and then test if point has moved when
org-babel-execute-src-block is called.
It might be easier to write your own
Hello,
I'm interested in having code blocks that do not eval when I run
(org-babel-execute-buffer) but do when the cursor is within them and I
explicitly want to execute them by entering C-c C-c.
I cannot get this behavior playing around with the :eval header argument. Is
the behavior I
