From: aaron barclay <firstname.lastname@example.org> To: Martyn Jago <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Export without code blocks Date: Mon, 30 Jan 2012 08:57:55 +1100 [thread overview] Message-ID: <CAHtOG9FcZysxP+Wrm9sErqJmRhf_n+fOUZUGwnHT7-gNrv22iQ@mail.gmail.com> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1140 bytes --] Thanks Martyn, that was a big help. aaron. On 27 January 2012 14:04, Martyn Jago <firstname.lastname@example.org> wrote: > Martyn Jago <email@example.com> writes: > > > Hi Aaron > > > > aaron barclay <firstname.lastname@example.org> writes: > > > >> Hi, > >> > >> I am having trouble finding the correct way to export a document without > >> the code blocks included. Should I be using #+EXPORT_EXCLUDE_TAGS? I > can't > >> seem to get it to work, anyone have the correct syntax? > >> > >> cheers, > >> aaron. > > > > #+EXPORT_EXCLUDE_TAGS is for defining tags (such as NO_EXPORT) to > > prevent headings or sub-headings (branches) being exported. As in: > > > > ** don't export me :NO_EXPORT: > > stuff > > > > Possibly what you need is :exports none or :exports results : > > > > begin_src python :exports results > > print "result" > > end_src > > Of course this won't work in python since it will 'print' result, but > not return it. so you also need :results output which makes, the `result' > that which is printed to STDOUT (standard out). > > > What format are you exporting too? > > > > Best, Martyn > > > [-- Attachment #2: Type: text/html, Size: 1849 bytes --]
prev parent reply other threads:[~2012-01-29 21:58 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-27 2:36 aaron barclay 2012-01-27 2:55 ` Martyn Jago 2012-01-27 3:04 ` Martyn Jago 2012-01-29 21:57 ` aaron barclay [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=CAHtOG9FcZysxP+Wrm9sErqJmRhf_n+fOUZUGwnHT7-gNrv22iQ@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Export without code blocks' \ /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
Code repositories for project(s) associated with this 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).