From: Neil Jerram <neil@ossau.homelinux.net>
To: Jarmo Hurri <jarmo.hurri@iki.fi>, emacs-orgmode@gnu.org
Subject: Re: Documentation: Babel scheme support and geiser
Date: Thu, 26 Jul 2018 08:41:21 +0100 [thread overview]
Message-ID: <87r2jqsau6.fsf@ossau.homelinux.net> (raw)
In-Reply-To: <87y3dz6x9v.fsf@iki.fi>
Jarmo Hurri <jarmo.hurri@iki.fi> writes:
> Greetings.
>
> I started doing some Schemeing in org,
Welcome to the club!
> and bumped into a couple of
> documentation issues I wanted to check / report.
>
> In short, I wonder whether
> 1. geiser should be listed as a scheme requirement in worg
> 2. ob-scheme.el should point to MELPA instead of ELPA for geiser.
>
> The long version
> ----------------
>
> First, worg lists no requirements for use of scheme
>
> https://orgmode.org/worg/org-contrib/babel/languages.html
>
> but typing C-c C-c in a scheme block gives error
>
> org-babel-execute-src-block: Symbol’s value as variable is void:
> geiser-default-implementation
Please note
https://www.mail-archive.com/emacs-orgmode@gnu.org/msg116779.html. I
believe that can be a runtime problem, i.e. to do with
require/autoloading, and maybe not an installation problem.
> Second, file ob-scheme.el tells me that
>
> ;; - for session based evaluation geiser is required, which is available from
> ;; ELPA.
>
> However, neither the ELPA page
>
> https://elpa.gnu.org/packages/
>
> nor "M-x list-packages" list geiser as an available package.
>
> It does seem, however, that geiser _is_ available from MELPA
That sounds right to me; I've checked that my geiser is from MELPA.
> http://stable.melpa.org/#/geiser
>
> (or git directly).
>
> All the best,
>
> Jarmo
Best wishes,
Neil
prev parent reply other threads:[~2018-07-26 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 17:27 Documentation: Babel scheme support and geiser Jarmo Hurri
2018-07-26 7:41 ` Neil Jerram [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=87r2jqsau6.fsf@ossau.homelinux.net \
--to=neil@ossau.homelinux.net \
--cc=emacs-orgmode@gnu.org \
--cc=jarmo.hurri@iki.fi \
/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).