From: Haider Rizvi <harizvi@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-mode export behavior change in 9.2?
Date: Sat, 12 Jan 2019 14:33:17 -0700 [thread overview]
Message-ID: <whyigd0p15zoi.fsf@hrizvi-wsm4.internal.salesforce.com> (raw)
In-Reply-To: 8B78585C-6836-44CE-AC26-D5AA495790F1@ucsd.edu
"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!
--
next prev parent reply other threads:[~2019-01-12 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 1:03 org-mode export behavior change in 9.2? Haider Rizvi
2019-01-12 18:24 ` Berry, Charles
2019-01-12 21:33 ` Haider Rizvi [this message]
2019-01-13 17:29 ` Berry, Charles
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=whyigd0p15zoi.fsf@hrizvi-wsm4.internal.salesforce.com \
--to=harizvi@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).