From: Michael Welle <firstname.lastname@example.org> To: email@example.com Subject: org-sbe and code blocks in a different files Date: Tue, 07 Jul 2020 20:43:18 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) Hello, I can execute code blocks in different (separate?) files like this: #+call: ../lob.org:convert-time-range-to-days(range="<2020-02-19 Wed>--<2020-02-21 Fri>") That is great. Can I call the same function from a table function? org-sbe doesn't support the above notation extended with an Org file name, I think. Second, I try to concentrate useful reusable code blocks in one file, lob.org in my case. That works. But I feel that I need some of the elisp based code blocks as code blocks, that I can execute, as well as separate elisp forms that I can eval from elisp code. How to deal with that? Ideas: Having two code blocks per function: one with the actual elisp code that can be tangled and a second one that just evals the form and can be used as a, well, code block usable with #+call? Or should I give them names like func and func_code (that's the one with actual elisp code) and write an elisp form that grabs all code blocks named *_code and evals them at start-up to bring the forms into the environment? Other ideas are also welcome. Regards hmw
next reply other threads:[~2020-07-07 18:45 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-07 18:43 Michael Welle [this message] 2020-07-08 14:10 ` Eric S Fraga 2020-07-08 14:11 ` Eric S Fraga 2020-07-08 14:59 ` Michael Welle 2020-07-08 15:07 ` Eric S Fraga 2020-07-08 20:29 Douglas Perrin 2020-07-09 7:09 ` Michael Welle 2020-07-09 16:43 ` Berry, Charles via General discussions about Org-mode. 2020-07-09 17:17 ` Michael Welle
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: org-sbe and code blocks in a different files' \ /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).