scheme SRC blocks

scheme SRC blocks

[Arun Isaac]

[-- Attachment #1: Type: text/plain, Size: 672 bytes --]


I have an org file with scheme SRC blocks like so.

#+BEGIN_SRC scheme
  (some-code-here)
#+END_SRC

Every time, I open the org file, I get prompted for the "Scheme
implementation" and I need to choose an implementation (guile, in my
case) before continuing. Similarly, I am also prompted for the same when
publishing the org file, or opening up the SRC block using
org-edit-special (C-c ') for editing. This happens because of the
behaviour of the command "scheme-mode" which prompts for the required
scheme implementation.

Manually choosing the scheme implementation every time is tedious and
annoying. Is there some way to circumvent this issue?

Thanks,
Arun Isaac.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

Re: scheme SRC blocks

[Robert Klein]

Hi,
Arun Isaac <theroarofthedragon@gmail.com> wrote:

> 
> I have an org file with scheme SRC blocks like so.
> 
> #+BEGIN_SRC scheme
>   (some-code-here)
> #+END_SRC
> 
> Every time, I open the org file, I get prompted for the "Scheme
> implementation" and I need to choose an implementation (guile, in my
> case) before continuing. Similarly, I am also prompted for the same
> when publishing the org file, or opening up the SRC block using
> org-edit-special (C-c ') for editing. This happens because of the
> behaviour of the command "scheme-mode" which prompts for the required
> scheme implementation.
> 
> Manually choosing the scheme implementation every time is tedious and
> annoying. Is there some way to circumvent this issue?

In addition to requiring 'geiser-install you have to set the
geiser-active-implementations variable, e.g.:

#+begin_src emacs-lisp
  (require 'geiser-install)
  (setq geiser-active-implementations '(guile))
#+end_src

See also http://www.nongnu.org/geiser/geiser_3.html#choosing_002dimpl
in the Geiser manual.

Best regards
Robert

Re: scheme SRC blocks

[Bernhard Pröll]

On Mon, 21. Mar 08:22, Robert Klein wrote:
>Hi,
>Arun Isaac <theroarofthedragon@gmail.com> wrote:
>
>>
>> I have an org file with scheme SRC blocks like so.
>>
>> #+BEGIN_SRC scheme
>>   (some-code-here)
>> #+END_SRC
>>
>> Every time, I open the org file, I get prompted for the "Scheme
>> implementation" and I need to choose an implementation (guile, in my
>> case) before continuing. Similarly, I am also prompted for the same
>> when publishing the org file, or opening up the SRC block using
>> org-edit-special (C-c ') for editing. This happens because of the
>> behaviour of the command "scheme-mode" which prompts for the required
>> scheme implementation.
>>
>> Manually choosing the scheme implementation every time is tedious and
>> annoying. Is there some way to circumvent this issue?
>
>In addition to requiring 'geiser-install you have to set the
>geiser-active-implementations variable, e.g.:
>
>#+begin_src emacs-lisp
>  (require 'geiser-install)
>  (setq geiser-active-implementations '(guile))
>#+end_src
>
>See also http://www.nongnu.org/geiser/geiser_3.html#choosing_002dimpl
>in the Geiser manual.
>
>Best regards
>Robert
>
>
Hi,

alternatively there is a :scheme header argument for src blocks:

#begin_src scheme :scheme guile

Regards
Bernhard

Re: scheme SRC blocks

[Arun Isaac]

[-- Attachment #1: Type: text/plain, Size: 597 bytes --]


> 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.


[-- Attachment #2.1: Type: text/plain, Size: 0 bytes --]



[-- Attachment #2.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

Re: scheme SRC blocks

[Bernhard Pröll]

On Mon, 21. Mar 23:55, Arun Isaac wrote:
>
>> 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.
>
Hi,

the org-babel-execute:scheme function looks for a :scheme header argument (otherwise uses the geiser-default-implementation). This may depend on your org version, mine is 8.3beta. The argument is listed in the org babel reference card:

http://org-babel.readthedocs.org/en/latest/extra-header-args/

Regards
Bernhard

Re: scheme SRC blocks

[Arun Isaac]

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

> the org-babel-execute:scheme function looks for a :scheme header
> argument (otherwise uses the geiser-default-implementation).

You're right. I went through ob-scheme.el. org-babel-execute:scheme does
look for a :scheme header argument.

But, my original problem was different. I was looking for a way to get
rid of the "Scheme implementation: " prompt when the org file was
opened, not when the src block was executed.

When the org file is opened, some org function is being called that
ends up prompting for the Scheme implementation. I'm not sure which
function is doing that.

> This may depend on your org version, mine is 8.3beta.

I am using org release_8.3.1-933-g809a83 -- the latest version on branch
master of the git repo.

[-- Attachment #2.1: Type: text/plain, Size: 0 bytes --]



[-- Attachment #2.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]