From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arun Isaac Subject: Re: scheme SRC blocks Date: Mon, 21 Mar 2016 23:55:29 +0530 Message-ID: <87d1qn8z8m.fsf@gmail.com> References: <87pouoaok5.fsf@gmail.com> <20160321082216.304b929d@pckr150.mpip-mainz.mpg.de> <20160321105645.GB11755@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43367) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ai4WU-0003wq-7K for emacs-orgmode@gnu.org; Mon, 21 Mar 2016 14:25:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ai4WQ-0000gk-6R for emacs-orgmode@gnu.org; Mon, 21 Mar 2016 14:25:50 -0400 Received: from mail-pf0-x233.google.com ([2607:f8b0:400e:c00::233]:33095) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ai4WP-0000ge-Tr for emacs-orgmode@gnu.org; Mon, 21 Mar 2016 14:25:46 -0400 Received: by mail-pf0-x233.google.com with SMTP id 4so143178066pfd.0 for ; Mon, 21 Mar 2016 11:25:45 -0700 (PDT) Received: from steel ([223.227.55.214]) by smtp.gmail.com with ESMTPSA id h2sm42327127pfd.91.2016.03.21.11.25.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 21 Mar 2016 11:25:43 -0700 (PDT) In-Reply-To: <20160321105645.GB11755@gmail.com> ("Bernhard \=\?utf-8\?Q\?Pr\?\= \=\?utf-8\?Q\?\=C3\=B6ll\=22's\?\= message of "Mon, 21 Mar 2016 11:56:45 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Emacs orgmode --=-=-= Content-Type: text/plain > In addition to requiring 'geiser-install you have to set the > geiser-active-implementations variable, e.g.: Customizing the geiser-active-implementations variable works for me. Thank you. > alternatively there is a :scheme header argument for src blocks: > > #begin_src scheme :scheme guile Unfortunately, this doesn't work for me. Is this header argument documented somewhere in the manual? This approach seems more self-contained to the org file, and it'll be good to have this, in case I want to send my org file to someone else, or if I decide to try out more scheme implementations. --=-=-= Content-Type: multipart/signed; boundary="==-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --==-=-= Content-Type: text/plain --==-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJW8DyZAAoJEC4l7othgCuzcoYH/2t6eR7cghQXn4po+VkgPT6y LUPZMe7uHw11/FEfY5jHUr+aKg/I70gnPkdtYug4DCeufzrVUjo5t6GnMuOyd1ZL 0nNMfyjFHQitz9idSUoGnzbRRykFJnOyah7zPucr8K8spcarcrBS00wI8kcXFAgP Dqu2ou8cylWCcNVYYOgvu+jJlL27QG0nn2vmWNJPtsVQrKM19C+YxmrEPzGrMi7k vJ7I064YDm0rY9ffj4WpbscbCjnFWK/Ngoe/E4ASV+gyiQp6AmFM1pU4wLKOJilJ tLbVpstbw6H32wqs+wAwxgsXNnTHC/rqOWaJR2kzkb+nlk6Mlhl5OGlue85XMr0= =/zUE -----END PGP SIGNATURE----- --==-=-=-- --=-=-=--