again, just tell me if I need to read more first, 'cause maybe I'm doing this wrong... ...but I'm struggling with the fact that I may have a bunch of stuff typed into the bottom window during a run session, and then, when I find there's a problem with my definitions, I want to fix them and see what happens.  Of course there's a warning in the window below that my definitions are stale.  So when I stop and start again, everything I had typed is gone! long winded aside ... It wasn't the best way to get the previously typed things to re-execute in the first place ... no up arrow, and you have to be at the end of a previous expression to transfer it to a new line.  I can see why you don't want the user to just edit it in place back in history, too ... although that would also be very convenient. (The approach that works means your cursor is no where near the place in the text that you wanted to tweak --- best would be if you could hit return even in the middle of a previous expression ........ (and we're back again) ..... at least you could get back to what you had typed. Should I just not be using DrScheme this way?  I can't imagine this is how it's done, always losing all your history of experiments just because you redefine a function. Thanks, as always.