<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Also: ESC-n goes to the Next line in the buffer after you have used ESC-p to access Previous lines.<div><br></div><div>Furthermore: control-e goes to the End of the line (so you can hit the return)</div><div><br></div><div>Also: control-a goes to the, uh, beginning of the line (Anterior? Affront? I think of 'a' as the first letter).  </div><div><br></div><div>There are a bunch more key combinations if you desire to become one of the people who argue that mousing-around is too slow ;)<br><div><br></div><div>rac</div><div><br><div><div>On Feb 22, 2009, at 9:22 AM, e wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">cool.  That solves the up-arrow prob!  I was sitting there googling "esc-p" until I got what you were saying :)  I thought you meant a "history about why it is the way it is" and I could find more about it at the "Epson Standard Code for Printers" <a href="http://en.wikipedia.org/wiki/ESC/P">http://en.wikipedia.org/wiki/ESC/P</a><br> <br>:)<br><br><br><br><div class="gmail_quote">On Sun, Feb 22, 2009 at 10:20 AM, Robby Findler <span dir="ltr"><<a href="mailto:robby@eecs.northwestern.edu">robby@eecs.northwestern.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> There is a history available via esc-p.<br> <font color="#888888"><br> Robby<br> </font><div><div></div><div class="Wj3C7c"><br> On Sun, Feb 22, 2009 at 8:18 AM, e <<a href="mailto:eviertel@gmail.com">eviertel@gmail.com</a>> wrote:<br> > again, just tell me if I need to read more first, 'cause maybe I'm doing<br> > this wrong...<br> ><br> > ...but I'm struggling with the fact that I may have a bunch of stuff typed<br> > into the bottom window during a run session, and then, when I find there's a<br> > problem with my definitions, I want to fix them and see what happens.  Of<br> > course there's a warning in the window below that my definitions are stale.<br> > So when I stop and start again, everything I had typed is gone!<br> ><br> > long winded aside ...<br> > It wasn't the best way to get the previously typed things to re-execute in<br> > the first place ... no up arrow, and you have to be at the end of a previous<br> > expression to transfer it to a new line.  I can see why you don't want the<br> > user to just edit it in place back in history, too ... although that would<br> > also be very convenient. (The approach that works means your cursor is no<br> > where near the place in the text that you wanted to tweak --- best would be<br> > if you could hit return even in the middle of a previous expression ........<br> ><br> > (and we're back again)<br> > ..... at least you could get back to what you had typed.<br> ><br> > Should I just not be using DrScheme this way?  I can't imagine this is how<br> > it's done, always losing all your history of experiments just because you<br> > redefine a function.<br> ><br> > Thanks, as always.<br> ><br> </div></div><div><div></div><div class="Wj3C7c">> _________________________________________________<br> >  For list-related administrative tasks:<br> >  <a href="http://list.cs.brown.edu/mailman/listinfo/plt-scheme" target="_blank">http://list.cs.brown.edu/mailman/listinfo/plt-scheme</a><br> ><br> ><br> </div></div></blockquote></div><br> _________________________________________________<br>  For list-related administrative tasks:<br>  <a href="http://list.cs.brown.edu/mailman/listinfo/plt-scheme">http://list.cs.brown.edu/mailman/listinfo/plt-scheme</a><br></blockquote></div><br></div></div></body></html>