From: John Kitchin <jkitchin@andrew.cmu.edu>
To: gmauer@gmail.com
Cc: Kyle Meyer <kyle@kyleam.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: How to get a block’s contents by name
Date: Sat, 28 Nov 2020 09:13:08 -0500 [thread overview]
Message-ID: <CAJ51ETqUOEhe3CwL+7CG+wz=WkLvXKSUuoi75yXDwTEdNdbJ9A@mail.gmail.com> (raw)
In-Reply-To: <CA+pajWKjJ5hB8jabdAhCqJ8kwns86Ev9hrC6bhnENHqWSeksZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]
I would do this:
#+BEGIN_SRC emacs-lisp
(defun org-get-named-block-contents (name)
(save-excursion
(goto-char (point-min))
(let ((regexp (org-babel-named-src-block-regexp-for-name name)))
(or (and (looking-at regexp)
(progn (goto-char (match-beginning 1))
(line-beginning-position)))
(ignore-errors (org-next-block 1 nil regexp)))
(org-babel-expand-src-block))))
#+END_SRC
This is basically what org-babel-find-named-block does, with the
(org-babel-expand-src-block) return instead of the position. It avoids the
double save-excursion.
This is probably faster than any alternative that involves parsing the
buffer, especially for large buffers.
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Fri, Nov 27, 2020 at 10:47 PM George Mauer <gmauer@gmail.com> wrote:
> Well that pains me on a software-engineer-aip-design level but that works!
> Thanks a lot.
>
> On Fri, Nov 27, 2020 at 8:22 PM Kyle Meyer <kyle@kyleam.com> wrote:
>
>> George Mauer writes:
>>
>> > I'm trying to figure out how I could fetch the contents of another
>> block by
>> > name from an elisp script
>> >
>> > I've seen `org-sbe` but I just want to get the block contents, (ideally
>> > with noweb and vars filled in - just as it would be tangled if we were
>> to
>> > tangle it)
>> >
>> > How do I do that?
>>
>> How about something like this?
>>
>> (save-excursion
>> (goto-char (org-babel-find-named-block "b"))
>> (org-babel-expand-src-block))
>>
>
[-- Attachment #2: Type: text/html, Size: 2694 bytes --]
prev parent reply other threads:[~2020-11-28 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 23:02 How to get a block’s contents by name George Mauer
2020-11-28 2:22 ` Kyle Meyer
2020-11-28 3:46 ` George Mauer
2020-11-28 14:13 ` John Kitchin [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='CAJ51ETqUOEhe3CwL+7CG+wz=WkLvXKSUuoi75yXDwTEdNdbJ9A@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=gmauer@gmail.com \
--cc=kyle@kyleam.com \
/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
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
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).