In article <qijent67nl3.fsf_-_@lambda.ai.mit.edu>,
Olin Shivers <shivers@ai.mit.edu> wrote:
[ lots and lots of stuff ]
>
>I further feel that the *right* solution for an interactive shell notation
>is... emacs. Just port Edwin to S48 and you would have the ultimate shell.
>You could put shell commands on control keys, always have a directory listing
>in a window, navigate the file system with cursor keys, perhaps a job list
>in another window. The shell commands bound to control keys would be defined
>with scsh. These would cover 90% of your interactions; for the hairy cases,
>you could directly enter Scheme code into an interaction buffer.
>
>I don't have time to get Edwin running in S48. I keep begging volunteers to
>port it -- I think the resulting shell would make such a person a Scheme hero.
>So far, no hits.
> -Olin
Apparently those interested enough to volunteer have shown enough wisdom
to pass over that project -- I looked at it long enough to download and
look through the edwin code, then decided it was a really time-consuming
project. I mentioned it to my major prof and he just looked at me like
I was out of my mind..
Of course, were you to offer someone something tangible for doing such
a project, you might find more interest...
More seriously, though, were I to find a decent PhD project somewhere
in the scsh/Scheme realm I'd probably jump on it. And probably others
are in the same boat (or even looking for senior project, MS projects, etc).
|