On Wed, 2006-02-15 at 21:12 +0000, Samium Gromoff wrote: > On Wed, 2006-02-15 at 12:58 -0500, Raymond Toy wrote: > > >>>>> "Samium" == Samium Gromoff <[EMAIL PROTECTED]> writes: > > Samium> That`s for top level frame, yes, but what about inner, debug > > frames? > > > > What do you want C-d to do on a debug frame? > > Preferably to jump out to the toplevel, or just one debug frame > outwards, i`m not sure what would make more sense... > > > Samium> This might look like a compromise to the UNIX side, as per the > > Samium> Unix Haters Handbook, but nevertheless it would be a great > > convenience > > Samium> to have this feature. > > >> > > >> Having accidentally exited clisp before, I find it rather annoying, > > >> especially when my Lisp contained lots of state that I wasn't ready > > to > > >> destroy it yet. > > > > Samium> Perhaps it could be made configurable? > > > > It was configurable. You could (setf *eofs* 0) and exit (sort of) on > > the first C-d/Return. > > > > I never bothered to check in this change. > > > > And you probably don't want to have to press C-d and Return, but > > that's how the current code works, because (I think), the input is > > line-buffered. > > Yes, i`m thinking along the lines of having an instant exit upon a C-d > in toplevel...
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. regards, Samium Gromoff P.S. Sorry for the notation ;-)
