emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Babel should not work in the subtree marked as not exported
Date: Tue, 11 Mar 2014 14:41:22 +0100	[thread overview]
Message-ID: <87lhwgettp.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: m2y50gc1b6.fsf@gorgonzola.whoi.edu

Hi Ken,

Ken Mankoff <mankoff@gmail.com> writes:

> On 2014-03-11 at 08:47, zwz wrote:
>> In my setup, there is 
>> (setq org-export-exclude-tags '("private" "exclude")
>>
>> and In my test.org:
>>
>> * test
>>
>> ** Not exported                :exclude:
>>    #+BEGIN_SRC ditaa :file test.png :cmdline -E
>>           +--------+---+---+---+---+---+---+---+  +---+---+---+---+---+---+---+---+
>>       x   | 0 cRED | 0 | 0 | 0 | 0 | 0 | 0 | 0 |  | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 |
>>           +--------+---+---+---+---+---+---+---+  +---+---+---+---+---+---+---+---+
>>    #+END_SRC
>>
>> ** blah blah
>>    blah blah blah
>>
>>
>> When I try to export it to pdf, the test.png is still generated,
>> although it is not used for the pdf at all.
>> So I think the export procedure may be optimized for more efficiency.
>
> No, because I often have code and sections I don't want exported, but
> I want their side-effects active. For example, code with sessions
> where part is not exported, but I need that code run so code
> elsewhere, using the same session, is able to run and be exported.
>
>   -k.


So what is your suggestion for the OP to achieve what he is after?
noexport and noeval at the same time.

Regards,
Andreas

  reply	other threads:[~2014-03-11 13:41 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11 12:47 Babel should not work in the subtree marked as not exported zwz
2014-03-11 13:27 ` Ken Mankoff
2014-03-11 13:41   ` Andreas Leha [this message]
2014-03-11 13:57     ` Ken Mankoff
2014-03-12 10:53       ` zwz
2014-03-12 22:58         ` Andreas Leha
2014-03-13 14:24           ` Eric Schulte
2014-03-13 22:48             ` Andreas Leha
2014-03-14  1:03               ` Eric Schulte
2014-03-14  5:44                 ` Samuel Wales
2014-03-14 13:02                   ` zwz
2014-03-14 19:10                   ` Samuel Wales
2014-03-14  5:48                 ` Samuel Wales
2014-03-14  8:40                   ` Sebastien Vauban
2014-03-14  8:41                 ` Andreas Leha
2014-03-14 19:59                   ` Eric Schulte
2014-03-15 13:54                     ` zwz
2014-03-15 14:46                     ` Nicolas Goaziou
2014-03-16  2:48                       ` Eric Schulte
2014-03-17 21:13                         ` Andreas Leha
2014-03-24 15:15                         ` Nicolas Goaziou
2014-03-24 16:05                           ` Eric Schulte
2014-03-24 16:21                             ` Bastien
2014-03-24 17:28                               ` Eric Schulte
2014-03-24 18:06                                 ` Samuel Wales
2014-03-24 18:49                                   ` Samuel Wales
2014-03-14  1:10               ` John Hendy
2014-03-14  8:34               ` Sebastien Vauban
2014-03-11 14:03   ` Rainer M Krug
2014-03-12  9:23     ` Sebastien Vauban
2014-03-12 10:46       ` zwz
2014-03-12 11:02     ` zwz
2014-03-12 15:00       ` John Hendy

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=87lhwgettp.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --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).