Samium Gromoff wrote: [snip] > > Thing is, there is a workflow where one often does a cycle resembling > this: > > 10 cmucl -eval '(load "somestuff.lisp")' > 20 *observe error messages* > 30 *type in (quit) by hand* > 40 *fix things* > 50 goto 10 > > So, just being able to Ctrl-d out of anyplace in debug stack > would be a major aid. >
This is a fairly unusual workflow in lisp. At the very least, you'd at least use the repl and (load "somestuff.lisp"), read the messages, fix somestuff.lisp and load it again. (Actually, you'd probably compile it too.) A far more typical and productive workflow would be to use slime (or ilisp) to do this. Then you can have slime put you in exactly the spot in somestuff.lisp where the errors occur. And if you do get into the debugger, pressing "q" in the slime debugger gets you out of the debugger. I think this is way most people never notice that Ctrl-D doesn't exit immediately. :-) Ray
