I don't, but it sure seems like CLISP isn't receiving your input, as bash (the shell) is giving the error. You might just post exactly was shows on screen because either CLISP is quiting and you don't notice or Bash+Cygwin is doing something funny where it is grabbing your commands before they get to CLISP. For instance, I can almost get what you got if I, for some reason, decided to start CLISP in the background (using &):
- Code: Select all
smithzv@ciabatta:~$ clisp &
[1] 22394
smithzv@ciabatta:~$ i i i i i i i ooooo o ooooooo ooooo ooooo
I I I I I I I 8 8 8 8 8 o 8 8
I \ `+' / I 8 8 8 8 8 8
\ `-+-' / 8 8 8 ooooo 8oooo
`-__|__-' 8 8 8 8 8
| 8 o 8 8 o 8 8
------+------ ooooo 8oooooo ooo8ooo ooooo 8
Welcome to GNU CLISP 2.48 (2009-07-28) <http://clisp.cons.org/>
Copyright (c) Bruno Haible, Michael Stoll 1992, 1993
Copyright (c) Bruno Haible, Marcus Daniels 1994-1997
Copyright (c) Bruno Haible, Pierpaolo Bernardi, Sam Steingold 1998
Copyright (c) Bruno Haible, Sam Steingold 1999-2000
Copyright (c) Sam Steingold, Bruno Haible 2001-2009
Type :h and hit Enter for context help.
;; Loading file /home/smithzv/.clisprc.lisp ...
;; Loading file /home/smithzv/quicklisp/setup.lisp ...
;; Loaded file /home/smithzv/quicklisp/setup.lisp
;; Loaded file /home/smithzv/.clisprc.lisp
[1]> (defvar *hi* 5)
defvar: command not found
Maybe Cygwin is forcing CLISP into the background??