From: "Berry, Charles" <ccberry@ucsd.edu>
To: Ken Mankoff <mankoff@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Painfully Slow Export
Date: Tue, 12 Jun 2018 21:07:53 +0000 [thread overview]
Message-ID: <04337B1C-B1CB-4349-87E1-5C7051B38BA7@ucsd.edu> (raw)
In-Reply-To: <CAFdBzEoXthjL21F6iYNkbJc=E-P67NyYhfmtr742ePmAd1c+7w@mail.gmail.com>
> On Jun 12, 2018, at 12:41 PM, Ken Mankoff <mankoff@gmail.com> wrote:
>
> Hi Chuck,
>
> It looks fine to me. I see:
>
> Name: fig:foo
> Lang: python
> Properties:
> :header-args :eval never-export
> :header-args:python nil
> Header Arguments:
> :cache no
> :eval never-export
> :exports results
> :hlines no
> :noweb yes
> :results file replace
> :session discharge_ts
> :tangle no
>
>
And still the src blocks execute?
Try this. Use the following in an org buffer:
--8<---------------cut here---------------start------------->8---
#+PROPERTY: header-args :eval never-export
#+begin_src emacs-lisp :exports results
"BBB"
#+end_src
#+RESULTS:
: AA
--8<---------------cut here---------------end--------------->8---
C-c C-c on the PROPERTY line and confirm as above that the header-args are rightly set.
Then `C-c C-e C-b t A' should give a buffer like this:
--8<---------------cut here---------------start------------->8---
,----
| AA
`----
--8<---------------cut here---------------end--------------->8---
Which you can see implies that the src-block did not run, but the results were properly exported.
This works for me on a brand new copy of master (9.1.13).
If it fails for you, then you need to check your org setup.
If it succeeds, but exporting your file still fails then there has to be something amiss in your file. I'd instrument `org-babel-execute-src-block' and see what the line with `(org-babel-check-evaluate info)' returns. It should be `nil'. If not you need to see what is in `info'.
HTH,
Chuck
next prev parent reply other threads:[~2018-06-12 21:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 14:01 Painfully Slow Export Ken Mankoff
2018-06-12 15:09 ` Chris
2018-06-12 19:41 ` Ken Mankoff
2018-06-12 15:51 ` Berry, Charles
2018-06-12 19:41 ` Ken Mankoff
2018-06-12 21:07 ` Berry, Charles [this message]
2018-06-12 21:15 ` Ken Mankoff
2018-06-12 21:30 ` Ken Mankoff
2018-06-12 22:07 ` Berry, Charles
2018-06-13 5:32 ` Ken Mankoff
2018-06-13 17:55 ` Berry, Charles
2018-06-13 18:32 ` Ken Mankoff
2018-06-14 4:42 ` Ken Mankoff
2018-06-14 18:34 ` BUG? WAS: " Berry, Charles
2018-06-23 21:06 ` Nicolas Goaziou
2018-06-24 1:53 ` Berry, Charles
2018-06-25 13:55 ` Ken Mankoff
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=04337B1C-B1CB-4349-87E1-5C7051B38BA7@ucsd.edu \
--to=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@gmail.com \
/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).