@billstclair Hey, got that installed. Works pretty slick. I have a few semi-questions if you have some time.
I'm here now. Crashed in the afternoon yesterday.
Glad to hear you got CCL working. Ask away.
@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
You'll need to find a lisp-unit expert for that one. My current system uses prove-asdf, which I know just well enough to add tests and run them.
I'm an old-fashioned lisper. I appreciate test suites, since they prevent regressions, but I tend to test my code bottom-up, one function at a time, as I write it, and only write test suites for some of the purely functional parts of my systems. I'm definitely not a test-driven-programming believer.
@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
Maybe I’m just accustomed to that kind of thing. It takes a few seconds to do:
c-x c-b
c-x o
c-n a few times
return
(or c-x b <buffer-name>)
c-c c-k
It’s also useful to bind slime-selector to a key in your ~/.emacs :
(global-set-key "\C-cs" 'slime-selector)
Then you can do C-c s r to get to the repl, and a bunch of other keys after C-c s to get other places (none of which I use much).
