[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is this expected Geiser behavior?

From: Nicholas Papadonis
Subject: Re: Is this expected Geiser behavior?
Date: Thu, 19 Mar 2020 23:47:14 -0400

Thanks for your help.  Perhaps I'm having trouble invoking Geiser with MIT Scheme.

I have been using these steps:

emacs &
;In *scratch*
M-x run-geiser
M-x geiser-mode
; *scratch* is stuck in LISP mode
M-x scheme-mode  
; MIT shown in buffer mode line, but I'm stuck editing in *scratch*

In this step I will try to use a buffer *.scm for geyser evaluation:

C-x C-f test.scm
;Scheme Guile/A mode is entered
M-x run-geiser
; In test.scm buffer 
M-x geiser-mode
; test.scm stuck in ELISP mode, MIT not shown in buffer mode line

more comments follow

On Thu, Mar 19, 2020 at 11:14 PM Jose A. Ortega Ruiz <address@hidden> wrote:
On Thu, Mar 19 2020, Nicholas Papadonis wrote:

> I'm running the Mit REPL and editing a file test.scm.  
> In the test.scm buffer:
> (display "test")
> C-x C-e
> Under the mode line displays:
> => #!unspecific
> C-u C-x C-e 
> (display "test") #!unspecific
> Is this expected behavior?

yes. the _expression_ (display "test") evaluates to the value
#!unspecific.  printing to the standard output is a side effect, not the
value returned by the _expression_.

> In the REPL display works:
> (display "test")
> test
> ;Unspecified return value

in geiser it also "works".  the standard output should appear in a
buffer called *Geiser dbg*.  for guile for instance, it has the

   (display "foo")

   => #<unspecified>


but it seems stdout is not fully implemented for MIT, and that's why you
don't see it.

Is this an issue in Geiser source or on the MIT side?



Adding manpower to a late software project makes it later.
 -Fred Brooks

reply via email to

[Prev in Thread] Current Thread [Next in Thread]