<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 22, 2009, at 10:10 AM, e wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">i gotcha. I guess the advantage of mousing around, though, is that it's universal across IDE's and languages. </blockquote><div><br></div>Yup. It amazing how a few simple concepts can allow so much universal utility. It is also true that a few favorite key combinations can increase productivity. For example, some allow you to jump around by s-expression, rather than toiling with individual letters.</div><div><br><blockquote type="cite"> You don't show up at someone's house or job and go, "I can't work without my favorite editor". Might be cool if you could go to a previous line, edit it, hit return wherever you are in the line, and then, it goes back to the way it was or something, but "it's all good". I'm just jumping in all out of order is my problem.</blockquote><div><br></div>It doesn't sound like you have a problem! Your thoughts are ones we all have. Until computers can read our minds directly, we have to deal with pesky editing conventions :)</div><div><br></div><div>rac</div><div><br><blockquote type="cite"><br> <br><br><br><div class="gmail_quote">On Sun, Feb 22, 2009 at 12:05 PM, Richard Cleis <span dir="ltr"><<a href="mailto:rcleis@mac.com">rcleis@mac.com</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;"> <div style="">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><div></div><div class="Wj3C7c"><div><br><div><div>On Feb 22, 2009, at 9:22 AM, e wrote:</div><br><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" target="_blank">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" target="_blank">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><br> On Sun, Feb 22, 2009 at 8:18 AM, e <<a href="mailto:eviertel@gmail.com" target="_blank">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>> _________________________________________________<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" target="_blank">http://list.cs.brown.edu/mailman/listinfo/plt-scheme</a><br> </blockquote></div><br></div></div></div></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></body></html>