From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
Nicolas Girard <girard.nicolas@gmail.com>
Subject: Re: [Babel] org-babel-execute-buffer gives different results than org-babel-exp-non-block-elements
Date: Mon, 26 Aug 2013 12:33:00 +0200 [thread overview]
Message-ID: <87bo4kkahv.fsf@gmail.com> (raw)
In-Reply-To: <87fvu0tq0w.fsf@gmail.com> (Eric Schulte's message of "Fri, 23 Aug 2013 08:55:59 -0600")
Hello,
Eric Schulte <schulte.eric@gmail.com> writes:
> If I understand correctly, I think ":export both :results none" should
> have the desired effect of executing the code block, not inserting the
> results, and keeping the code block itself in place.
AFAICT, ":export both :results none" combination doesn't seem to produce
the desired outcome with the example file.
Note that the feature is only needed for elisp, since it is the only
language able to modify the buffer containing the source code.
> If you want to run emacs lisp at export time but don't want the code or
> the results, maybe it would be a more natural fit for a filter
> function?
I think the OP wants (org-babel-execute-buffer) and
(org-export-execute-babel-code) to behave the same in this specific
situation. So, it's not export-specific.
To put it differently, he wants to disable code replacement with value
(which is specific to the export part of Babel).
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2013-08-26 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 18:23 [Babel] org-babel-execute-buffer gives different results than org-babel-exp-non-block-elements Nicolas Girard
2013-08-22 18:41 ` Nicolas Goaziou
2013-08-22 19:28 ` Nicolas Girard
2013-08-22 20:28 ` Nicolas Girard
2013-08-22 20:33 ` Nicolas Goaziou
2013-08-22 21:01 ` Nicolas Girard
2013-08-22 23:06 ` Nicolas Goaziou
2013-08-22 23:20 ` Nicolas Girard
2013-08-23 8:11 ` Nicolas Goaziou
2013-08-23 14:55 ` Eric Schulte
2013-08-26 10:33 ` Nicolas Goaziou [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=87bo4kkahv.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=girard.nicolas@gmail.com \
--cc=schulte.eric@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).