From: John Ciolfi <email@example.com> To: Nicolas Goaziou <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/)] Date: Fri, 12 Jun 2020 14:32:26 +0000 [thread overview] Message-ID: <MN2PR05MB6766969CA28262EFD747DAA0D1810@MN2PR05MB6766.namprd05.prod.outlook.com> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1755 bytes --] Hi Perhaps, in the interactive C-c C-e mode there could be: [C-e] Eval code blocks: always | never | use-eval-header-setting where 'use-eval-header-settings' is the default and uses whatever was set by the current org file and emacs session. Always and never would override that. Consider the scenario where a number of people are working on a common overall "book" which is constructed from many org-files. The "hardcoded" setting of :eval no-export header in individual blocks would mean that I cannot interactively enable or disable the evaluation of the blocks. Part of my confusion was that it took a little bit to figure this out (I ended up debugging the lisp code to get what I wanted). I think this could be improved in the doc, though I do admit, I'm not entirely clear on all the ways to control evaluation of code blocks during export. If I were, I'd propose something for the org manual. Thanks John ________________________________ From: Nicolas Goaziou <firstname.lastname@example.org> Sent: Friday, June 12, 2020 4:51 AM To: John Ciolfi <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/)] Hello, John Ciolfi <firstname.lastname@example.org> writes: > 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'm not sold to this idea. There are already many ways to control evaluation of Babel code, i.e., :eval header arguments in its multiple forms, `org-export-use-babel'. Adding one more could also add confusion. Regards, -- Nicolas Goaziou [-- Attachment #2: Type: text/html, Size: 4148 bytes --]
next prev parent reply other threads:[~2020-06-12 14:32 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 2020-06-12 8:51 ` Nicolas Goaziou 2020-06-12 14:32 ` John Ciolfi [this message] 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=MN2PR05MB6766969CA28262EFD747DAA0D1810@MN2PR05MB6766.namprd05.prod.outlook.com \ --email@example.com \ --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/)]' \ /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).