From: Neil Jerram <neil@ossau.homelinux.net>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Scheme code evaluation in fresh Emacs
Date: Tue, 19 Dec 2017 18:29:35 +0000 [thread overview]
Message-ID: <f7e3220e-cb5f-928b-e659-fb2ab1b276ce@ossau.homelinux.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 288 bytes --]
When I try to evaluate Scheme code in an Emacs where I haven't yet done
any Geiser/Scheme work, I get an error about
geiser-default-implementation being undefined. The attached patch fixes
that, but I am not sure if it is the most minimal fix possible. WDYT?
Best wishes - Neil
[-- Attachment #2: 0001-Fix-Scheme-evaluation-in-fresh-Emacs.patch --]
[-- Type: text/x-patch, Size: 951 bytes --]
From adceb034b886d1c3624b31f83f8826869cd1b92c Mon Sep 17 00:00:00 2001
From: Neil Jerram <neil@tigera.io>
Date: Tue, 19 Dec 2017 18:15:00 +0000
Subject: [PATCH] Fix Scheme evaluation in fresh Emacs
* lisp/ob-scheme.el: Require geiser-impl so that
geiser-default-implementation is defined. Otherwise, unless Geiser
has previously been run (e.g. with `run-geiser'), you'll see an
error that geiser-default-implementation is undefined.
---
lisp/ob-scheme.el | 1 +
1 file changed, 1 insertion(+)
diff --git a/lisp/ob-scheme.el b/lisp/ob-scheme.el
index f67080adf..7dbd78097 100644
--- a/lisp/ob-scheme.el
+++ b/lisp/ob-scheme.el
@@ -40,6 +40,7 @@
;;; Code:
(require 'ob)
(require 'geiser nil t)
+(require 'geiser-impl nil t)
(defvar geiser-repl--repl) ; Defined in geiser-repl.el
(defvar geiser-impl--implementation) ; Defined in geiser-impl.el
(defvar geiser-default-implementation) ; Defined in geiser-impl.el
--
2.15.1
next reply other threads:[~2017-12-19 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 18:29 Neil Jerram [this message]
2017-12-19 19:30 ` Scheme code evaluation in fresh Emacs Nicolas Goaziou
2017-12-19 19:52 ` Neil Jerram
2017-12-19 21:49 ` Nicolas Goaziou
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=f7e3220e-cb5f-928b-e659-fb2ab1b276ce@ossau.homelinux.net \
--to=neil@ossau.homelinux.net \
--cc=emacs-orgmode@gnu.org \
/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).