From: Munyoki Kilyungi <me@bonfacemunyoki.com>
To: Tim Van den Langenbergh <tmt_vdl@gmx.com>
Cc: guile-user@gnu.org
Subject: Re: Using guile (running on a port) in Org Mode
Date: Fri, 15 Jul 2022 17:44:18 +0300 [thread overview]
Message-ID: <86fsj2zb99.fsf@bonfacemunyoki.com> (raw)
In-Reply-To: <871qumless.fsf@terra.tmtvl.info>
[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]
Tim Van den Langenbergh <tmt_vdl@gmx.com>
anaandika:
> Munyoki Kilyungi <me@bonfacemunyoki.com> writes:
>
>> [[PGP Signed Part:Undecided]]
>>
>> Hi Guilers!
>>
>> Recently I worked out a way to point an org src
>> block to any python environment I want:
>> <https://www.bonfacemunyoki.com/post/2022-07-12-gnu-guix-org-mode-guix-profiles/>.
>> WRT to scheme code, is there a way to tell a
>> scheme source block to run a guile interpreter
>> that runs on a given port?
>
> Hello there,
>
> it's been a little while since I looked at the ob-scheme code, but I believe
> that you should be able to use an existing Geiser session as the execution
> session for your Org buffer. So if you connect Geiser to a running Guile
> instance, give the Geiser buffer a unique name, and use that name as the
> session parameter for your src block (plus or minus earmuffs) I think it should
> work.
>
So I've renamed my buffer to "GUILE"
and now I have this:
#+begin_src scheme :results output :session "GUILE"
(+ 1 1)
#+end_src
But I get:
#+RESULTS:
: Geiser Interpreter produced no output
Anything I'm doing wrong? I'll look into the
ob-scheme source later though. Perhaps I'll find
answers there.
--
(Life is like a pencil that will surely run out,
but will leave the beautiful writing of life.)
(D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
(hkp://keys.gnupg.net))
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2022-07-15 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 12:03 Using guile (running on a port) in Org Mode Munyoki Kilyungi
2022-07-15 12:48 ` Tim Van den Langenbergh
2022-07-15 14:44 ` Munyoki Kilyungi [this message]
2022-07-15 14:57 ` Zelphir Kaltstahl
2022-07-16 19:19 ` Munyoki Kilyungi
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.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86fsj2zb99.fsf@bonfacemunyoki.com \
--to=me@bonfacemunyoki.com \
--cc=guile-user@gnu.org \
--cc=tmt_vdl@gmx.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.
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).