Also: ESC-n goes to the Next line in the buffer after you have used
ESC-p to access Previous lines.
Furthermore: control-e goes to the End of the line (so you can hit the
return)
Also: control-a goes to the, uh, beginning of the line (Anterior?
Affront? I think of 'a' as the first letter).
There are a bunch more key combinations if you desire to become one of
the people who argue that mousing-around is too slow ;)
rac
On Feb 22, 2009, at 9:22 AM, e wrote:
> 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" http://en.wikipedia.org/wiki/ESC/P>> :)
>>>> On Sun, Feb 22, 2009 at 10:20 AM, Robby Findler <robby at eecs.northwestern.edu> > wrote:
> There is a history available via esc-p.
>> Robby
>> On Sun, Feb 22, 2009 at 8:18 AM, e <eviertel at gmail.com> wrote:
> > 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.
> >
> > _________________________________________________
> > For list-related administrative tasks:
> > http://list.cs.brown.edu/mailman/listinfo/plt-scheme> >
> >
>> _________________________________________________
> For list-related administrative tasks:
>http://list.cs.brown.edu/mailman/listinfo/plt-scheme
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20090222/bc6ade49/attachment.html>