emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Frederick Giasson <fred@fgiasson.com>
To: emacs-orgmode@gnu.org
Subject: Re: HTML export with ":export" parameter with Orgmode 9.0
Date: Fri, 11 Nov 2016 12:10:36 -0500	[thread overview]
Message-ID: <684906f0-7155-0abb-cca1-71a5da100988@fgiasson.com> (raw)
In-Reply-To: <87mvh6fjiv.fsf@nicolasgoaziou.fr>

Hi Nicolas,

> It seems other users experienced it, yet it is unexpected and I cannot
> reproduce it even with a minimal init file.

Ok I think I found the issue.

In all the files I worked on since I upgraded to 9.0 I had the following 
setting at the top of my org files:

=========
# -*- org-export-babel-evaluate: nil -*-
=========

In these notebooks, I don't want org-export to evaluate the code blocks, 
I want to do it manually (since some of them takes quite a while to run 
and I don't want to wait minutes to get an export).

In 8.x this was working perfectly. However, it appears that this 
behavior changed in 9.0. If I have that in place, then the :export 
header parameter is basically ignored and defaulted to "both".

Did this change and is this to be expected? If so, what should I use to 
get the same behavior?

Thanks!

Fred


>
> Regards,
>

      parent reply	other threads:[~2016-11-11 17:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08 13:30 HTML export with ":export" parameter with Orgmode 9.0 Frederick Giasson
2016-11-11  9:33 ` Nicolas Goaziou
2016-11-11 14:11   ` Frederick Giasson
2016-11-11 17:21     ` Charles C. Berry
2016-11-11 18:15       ` Frederick Giasson
2016-11-12  3:21         ` Charles C. Berry
2016-11-12 11:00           ` Nicolas Goaziou
2016-11-13  3:09             ` [PATCH] " Charles C. Berry
2016-11-13  8:02               ` Nicolas Goaziou
2016-11-13 23:38                 ` Charles C. Berry
2016-11-14  7:43                   ` Nicolas Goaziou
2016-11-14 13:32           ` Frederick Giasson
2016-11-11 17:10   ` Frederick Giasson [this message]

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=684906f0-7155-0abb-cca1-71a5da100988@fgiasson.com \
    --to=fred@fgiasson.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).