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 13:15:20 -0500	[thread overview]
Message-ID: <98645dec-97ad-3d3f-3b1a-291c0dce122d@fgiasson.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1611110917430.786@charles-berrys-macbook.local>

Hi Chuck,

> even with a minimal init file.
>
> If you ever set the value of `org-export-babel-evaluate' to nil this 
> might produce the behavior you describe. 

Maybe, but as stated in the manual: "Setting the 
org-export-babel-evaluate variable to nil will ensure that no code 
blocks are evaluated as part of the export process."

 From here: http://orgmode.org/manual/Exporting-code-blocks.html

The thing is that I indeed want to make sure that the code blocks are 
evaluated, but to me evaluation of code block is different than what to 
export from the Org file. It is often the case that I don't want export 
to evaluate anything, but just to export what is in the Org file's 
markup (while following what the header parameters say).

Thanks,

Fred

  reply	other threads:[~2016-11-11 18:15 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 [this message]
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

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=98645dec-97ad-3d3f-3b1a-291c0dce122d@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).