emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Nicolas Girard <girard.nicolas@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [Babel] org-babel-execute-buffer gives different results than org-babel-exp-non-block-elements
Date: Fri, 23 Aug 2013 10:11:20 +0200	[thread overview]
Message-ID: <87k3jckes7.fsf@gmail.com> (raw)
In-Reply-To: <CANMKmecqCo9SeCrET1-ecv8E5=pk0Rw=M-nWMZViCy437d94Jw@mail.gmail.com> (Nicolas Girard's message of "Fri, 23 Aug 2013 01:20:09 +0200")

Nicolas Girard <girard.nicolas@gmail.com> writes:

>> `org-babel-exp-non-block-elements' and `org-babel-exp-process-buffer'
>> could probably check if code still exists before trying to remove (and
>> replace) it.
>>
>
> Yeah, I don't know how much work it would represent but it seems much
> more appropriate that my hack-ish solution.

It might be tricky to set up. I'm not even sure Babel is meant for these
cases (where evaluating code removes its source).

Another possibility is to have a "side-effect only" behaviour for export
where code block is not removed nor replaced. ":exports none" could be
a candidate for this. Maybe Eric Schulte has an opinion on it.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-08-23  8:11 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 [this message]
2013-08-23 14:55                 ` Eric Schulte
2013-08-26 10:33                   ` Nicolas Goaziou

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=87k3jckes7.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=girard.nicolas@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).