org-mode export behavior change in 9.2?

org-mode export behavior change in 9.2?

[Haider Rizvi]

I've been using literate programming approach with org-babel for a
while. I just noticed that with 9.2, when I try to export (c-c c-e h
o) an org doc / section, any shell blocks with a named session are
executed as it is exporting to html!

I don't think it was this way before?  Is there a way to not have it
execute each shell block when trying to export.

I just tested it with this small .org document. On osx, /usr/bin/say
speaks out the arguments.

-------------------------
#+begin_src shell :session sh-pcnw3
/usr/bin/say something         # say it out loud!
#+end_src
-------------------------

Without the :session, it doesn't!

-- 

Re: org-mode export behavior change in 9.2?

[Berry, Charles]

> On Jan 11, 2019, at 5:03 PM, Haider Rizvi <harizvi@gmail.com> wrote:
> 
> I've been using literate programming approach with org-babel for a
> while. I just noticed that with 9.2, when I try to export (c-c c-e h
> o) an org doc / section, any shell blocks with a named session are
> executed as it is exporting to html!
> 
> I don't think it was this way before?

 
AFAICS, nothing has changed in the way :session is handled for shell src blocks in a very long time. 

Perhaps, you had set `:eval never-export' previously, but not now. ??

>  Is there a way to not have it
> execute each shell block when trying to export.

This seems to work as you would want:

#+begin_src shell :session sh-pcnw3 :eval never-export
/usr/bin/say something         # say it out loud!
#+end_src


If you can identify a release in which the behavior was as you said, it might be possible to dig deeper.

HTH,

Chuck

Re: org-mode export behavior change in 9.2?

[Haider Rizvi]

"Berry, Charles" <ccberry@ucsd.edu> writes:

>> On Jan 11, 2019, at 5:03 PM, Haider Rizvi <harizvi@gmail.com> wrote:
>> 
>> I've been using literate programming approach with org-babel for a
>> while. I just noticed that with 9.2, when I try to export (c-c c-e h
>> o) an org doc / section, any shell blocks with a named session are
>> executed as it is exporting to html!
>> 
>> I don't think it was this way before?
>
>  
> AFAICS, nothing has changed in the way :session is handled for shell src blocks in a very
> long time.
>
> Perhaps, you had set `:eval never-export' previously, but not now. ??
>
>>  Is there a way to not have it
>> execute each shell block when trying to export.
>
> This seems to work as you would want:
>
> #+begin_src shell :session sh-pcnw3 :eval never-export
> /usr/bin/say something         # say it out loud!
> #+end_src
>
>
> If you can identify a release in which the behavior was as you said, it might be possible to
> dig deeper.

Chuck, thanks for responding.

I've never had the never-export set. I'll try to go back and pinpoint
when the change shows up if I can.

Is the difference between named session and without it expected? With
the named session, the block is executed on export, and without it, it
is not executed!

-- 

Re: org-mode export behavior change in 9.2?

[Berry, Charles]

> On Jan 12, 2019, at 1:33 PM, Haider Rizvi <harizvi@gmail.com> wrote:
> 
> "Berry, Charles" <ccberry@ucsd.edu> writes:
> 
>>> On Jan 11, 2019, at 5:03 PM, Haider Rizvi <harizvi@gmail.com> wrote:
>>> 
>>> I've been using literate programming approach with org-babel for a
>>> while. I just noticed that with 9.2, when I try to export (c-c c-e h
>>> o) an org doc / section, any shell blocks with a named session are
>>> executed as it is exporting to html!
>>> 
>>> I don't think it was this way before?
>> 
>> 
>> AFAICS, nothing has changed in the way :session is handled for shell src blocks in a very
>> long time.
>> 
>> Perhaps, you had set `:eval never-export' previously, but not now. ??
>> 
>>> Is there a way to not have it
>>> execute each shell block when trying to export.
>> 
>> This seems to work as you would want:
>> 
>> #+begin_src shell :session sh-pcnw3 :eval never-export
>> /usr/bin/say something         # say it out loud!
>> #+end_src
>> 
>> 
>> If you can identify a release in which the behavior was as you said, it might be possible to
>> dig deeper.
> 
> Chuck, thanks for responding.
> 
> I've never had the never-export set. I'll try to go back and pinpoint
> when the change shows up if I can.
> 
> Is the difference between named session and without it expected? With
> the named session, the block is executed on export, and without it, it
> is not executed!


With the default `:exports code' (your case) or with `:exports none' the difference is expected. You can read `org-babel-exp-do-export' for details.

If I were you I wouldn't spend much time trying to run this down.  I'd just use `:eval never-export'.  It seems like that is the behavior you want.


Chuck