emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Douglas Perrin <doug2024@gmail.com>
To: emacs-orgmode@gnu.org
Cc: mwe012008@gmx.net
Subject: Re: org-sbe and code blocks in a different files
Date: Wed, 8 Jul 2020 16:29:24 -0400	[thread overview]
Message-ID: <CAFw+bXF4Ets6m7Lz+1n=WVydsyO2Yq25YunRcWZkMJjHz0QdQQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 933 bytes --]

Hi Michael,
Maybe I am not understanding what you want to do but I use
org-babel-lob-ingest/org-sbe to execute blocks from other files on
start-up like this:
# Local Variables:
# eval: (org-babel-lob-ingest "Template-Loader.org")
# eval: (org-sbe "Init-Template") ;; the name of a block
in Template-Loader.org file
# End:

I assume this means that org-sbe can see the block names from the other
file. But I haven't tested the behavior with #call just executing elisp.

Date: Wed, 08 Jul 2020 16:59:32 +0200
From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: org-sbe and code blocks in a different files
Message-ID: <877dve9hnv.fsf@luisa.c0t0d0s0.de>
Content-Type: text/plain

Hi Eric,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> * org-babel-lob-ingest
ah, I learned something new here. Unfortunately, it seems like org-sbe
doesn't look into the list spit out by org-babel-lob-ingest.


[-- Attachment #2: Type: text/html, Size: 1566 bytes --]

             reply	other threads:[~2020-07-08 20:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 20:29 Douglas Perrin [this message]
2020-07-09  7:09 ` org-sbe and code blocks in a different files Michael Welle
2020-07-09 16:43   ` Berry, Charles via General discussions about Org-mode.
2020-07-09 17:17     ` Michael Welle
  -- strict thread matches above, loose matches on Subject: below --
2020-07-07 18:43 Michael Welle
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

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:

  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='CAFw+bXF4Ets6m7Lz+1n=WVydsyO2Yq25YunRcWZkMJjHz0QdQQ@mail.gmail.com' \
    --to=doug2024@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mwe012008@gmx.net \


* 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


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).