[slim-vim] ecl-repl 1.0.0 now available
Brad Beveridge
brad.beveridge at gmail.com
Mon Apr 3 10:55:20 CDT 2006
I'll try to get a simple reproducible case tonight.
When I work with the ECL repl, I usually have the window split, with
the ECL REPL in the lower half. I also use hidden buffers to edit
multiple files, and have tab mapped to :bnext to move between them.
Unfortunately, this means I move through the REPL and scratch buffers.
You can cause these buffers to be skipped by moving to them and ":set
nobuflisted". However, they are also removed from :ls, so make sure
you know what buffer number the REPL and scratch are so you can
:b<number> back to it if you accidentally lose that buffer.
Brad
On 4/3/06, Larry Clapp <larry at theclapp.org> wrote:
> On Sun, Apr 02, 2006 at 03:02:02PM -0800, Brad Beveridge wrote:
> > Is it possible to make ECL warnings/errors appear in the REPL when
> > forms like (load "foo") are executed?
>
> Probably. I'll take a look at it.
>
> Note that when I try (load "foo"), where "foo.lisp" doesn't exist, I
> get this
>
> Error: Filesystem error with pathname #P"foo".^@Either^@ 1) the file
> does not exist, or^@ 2) we are not allow to access the file, or^@ 3)
> the pathname points to a broken symbolic link.
>
> at the bottom of the screen (except all one line), and this
>
> COMMON-LISP-USER> (load "foo")
> Error: Filesystem error with pathname #P"foo".
> Either
> 1) the file does not exist, or
> 2) we are not allow to access the file, or
> 3) the pathname points to a broken symbolic link.
> NIL
>
> in the repl output buffer. Obviously the stuff at the bottom of the
> screen should go away, but the stuff in the repl output buffer seems
> okay.
>
> If I create play2.lisp:
>
> % cat ~/lisp/play2.lisp
> (defun fact ()
>
> and then (load "/home/lmc/lisp/play2"), I get this
>
> COMMON-LISP-USER> (load "/home/lmc/lisp/play2")
> Error: Unexpected end of file on #<input stream #P"/home/lmc/lisp/play2.lisp">.
> ;;; Loading #P"/home/lmc/lisp/play2.lisp"
> NIL
>
> in the repl output buffer, which seems okay. I haven't tried any
> other test cases, so ...
>
> > It appears that it warnings at least go to another output, similar
> > to what happens when you run :make, except that the errors are not
> > present in the Error List buffer.
>
> ... can you elaborate on what you try, what you see, and what you
> want?
>
> -- Larry
>
> _______________________________________________
> slim-vim mailing list
> slim-vim at lispniks.com
> http://www.lispniks.com/mailman/listinfo/slim-vim
>
More information about the slim-vim
mailing list