From: Helder Ribeiro <helder@...>
Date: 2007-01-22T20:48:59+09:00
Subject: Re: Ruby text editor for beginner

James Edward Gray II wrote:
> On Jan 21, 2007, at 8:20 PM, Helder Ribeiro wrote:
>
> A big project is just a ton of little projects, once you chop it up.
> Test driven development is all about that, I think.

Yes, but sometimes you can't chop it up so fine-grained that you have
self-contained, one-lined commands (that's what I meant by
'scripting').

Say you write up a method and want to correct it, you have retype or
find through the history by pressing "Up" all the lines that "worked"
and re-entering them. You also can't just read them from a file either,
AFAIK (not smthg like an incomplete method code, for instance).

Conversely, it's not trivial to go through the lines that "worked" in
that awkward "Up"-key fashion, then select them and save them out to a
file.

Those are the questions Jonathan Allen pointed out, and I don't have
good answers for them.

Perhaps there's some different mode in irb where you can quickly
inspect the aggregated command history as in a regular editor and
choose to append selected lines out to a file? That'd be very helpful,
especially with the ability to load them back as if you had typed them
in yourself, which would allow for loading of incomplete blocks of
code.

> 
> James Edward Gray II