From: John Ciolfi <firstname.lastname@example.org> To: Nicolas Goaziou <email@example.com> Cc: "firstname.lastname@example.org" <email@example.com> Subject: Re: Bug: Option to disable evaluation of code blocks during export [9.3.7 (9.3.7-dist @ /PATH/TO/org/install/emacs/site-lisp/org/)] Date: Thu, 11 Jun 2020 21:57:51 +0000 [thread overview] Message-ID: <DM6PR05MB6764AE108FCFF28396CB3A2AD1800@DM6PR05MB6764.namprd05.prod.outlook.com> (raw) In-Reply-To: <firstname.lastname@example.org> [-- Attachment #1: Type: text/plain, Size: 1239 bytes --] It would be very nice if I could enable/disable the evaluation of code blocks during the export process in the interactive C-c C-e environment. I do now see that I can use the :eval no-export header more effectively, so this is less of an issue, but still think it would be a nice enhancement to have control from within the interactive org-export-dispatch function. Thanks John ________________________________ From: Nicolas Goaziou <email@example.com> Sent: Thursday, June 11, 2020 5:28 PM To: John Ciolfi <firstname.lastname@example.org> Cc: email@example.com <firstname.lastname@example.org> Subject: Re: Bug: Option to disable evaluation of code blocks during export [9.3.7 (9.3.7-dist @ /PATH/TO/org/install/emacs/site-lisp/org/)] Hello, John Ciolfi <email@example.com> writes: > Could you add an option to disable evaluation of code blocks when exporting? If I > have an org-file with many code blocks setup for evaulation (babel), when I export, I get > prompted for every code block. Also the prompt does not clearly show which code block it's > asking to evaluate. What is wrong with :eval no-export header? You can set it globally, file-wise, tree wise, or per block. Regards, -- Nicolas Goaziou [-- Attachment #2: Type: text/html, Size: 2622 bytes --]
next prev parent reply other threads:[~2020-06-11 21:58 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-11 19:55 John Ciolfi 2020-06-11 21:28 ` Nicolas Goaziou 2020-06-11 21:57 ` John Ciolfi [this message] 2020-06-12 8:51 ` Nicolas Goaziou 2020-06-12 14:32 ` John Ciolfi 2020-06-13 9:46 ` Nicolas Goaziou 2020-06-13 12:22 ` Jeremie Juste
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=DM6PR05MB6764AE108FCFF28396CB3A2AD1800@DM6PR05MB6764.namprd05.prod.outlook.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Bug: Option to disable evaluation of code blocks during export [9.3.7 (9.3.7-dist @ /PATH/TO/org/install/emacs/site-lisp/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
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).