La Fée Verte @Absinthe@qoto.org
The green faerie
Joined Aug 2019
Okay Bill, here's what I found. It's not perfect, but it's getting there.
In the REPL I (load ) the test file
The tests run.
Then I do c-c c-e - This brings up Slime Eval:
where I enter (lisp-unit:run-tests :all :workfile-test)
The tests run again.
Then c-c c-e <up> <enter>
Which I think is (slime-interactive-eval STRING)
@billstclair meta-. is that goto definiton?
@billstclair that seems useful too
@billstclair well, I have been keeping the REPL, and both files open on screen. It was not to bad to mouse to the window and c-x c-k... Or I could C-x <arrow> back and forth but if I could just run (load "test-myfile.lisp") or maybe (run-all-tests) it would be sufficient I think.
While I am in the test-myfile.lisp it is no biggie to run c-x c-k. It is when I am in the myfile.lisp that I want to "run the test" without having to leave the focus on the file I am programming in
@billstclair I am wanting to do something akin to TDD.
Write a test, run and see it fail. Write some code until running the test passes. Clean up the code. Start again with the next test.
At this point if I could send something to the mRepl that would re-run the load or (run-test) or something that might be all I need. As it is, I keep having to swap back and forth to the test tile and compile-load that
@endlessmike @billstclair I am not sure what it takes to run Cloture, but it sure wouldn't take much to compile and install CCL, just give it a shot.
@billstclair so as I move over to EMACS and SLY (or SLIME) I am looking at how to run my unit tests. For the time being they are all in lisp-unit. What I have provided is that there is a ql load for lisp-unit at the top of the tests file and a load for the corresponding work file, and in the bottom they call the run-all-tests. So if I (load "test-file.lisp) It actually runs the tests. But then if I edit the work file, Then I have to swap back and then c-c c-k on the tests file it seems to run on the repl. But this seems quite awkward, so I assume I am doing it wrong
@billstclair Hey, got that installed. Works pretty slick. I have a few semi-questions if you have some time.
@billstclair excellent, I may just do that tonight. I feel so special! Like I have an "in" :)
@billstclair that's what I thought. So it sounds like CCL is alive and kicking, that would be a decent one to use over gcl, sbcl, or CLISP?
@billstclair so #slime and not #sly then? I think I have quicklisp, that is loading the stuff qith ql:quicklad to get lisp-unit.
@freemo Didn't even mention Haskell.. doing that too though :)
@freemo Yes, those are the isights I am looking for. COmpared to other IDE's
@wrdnxnk@freeradical.zone Yeah, I am hating #clojure now, every time I make the slightest error I have to slog through all that nasty java back trace. ..
#clozurecl is a #commonlisp despite the deceptively similar name to cloJure it is spelled with a Z cloZureCL.
I guess, while I am at it, which #lisp #commonlisp should I settle on
#ClozureCL, #GnuCommonLisp #gcl, #Clisp, #SteelBankCommonLisp (#sbcl)
@billstclair Well, that is the choices #emacs + #slime or #sly ....
Or #spacemacs with #lisp layer. Probably ultimately 6 of 1...
#spacemacs ... sell me.
I have started to do a bit more #isp and lisp like language things. This just generally pushes me into the #emacs world (just feels wrong doing lisp stuff in Vim). But if I am going to gear up and retool Emacs to use, maybe it is time to reconsider Spacemacs.
I am open minded enough to consider facts in making a decision. :)
@johnlitt yes I can
