harsh

There isn't a whole lot to say about it yet. I've built a unix shell that does the following:

• read input without blocking on the input stream
• kick off processes as a result of handled input
• really super basic stdout -> stdin piping

purpose:

This is mostly an excercise in learning all the pieces involved in terminal emulation, shells, job execution, scripting, and such. So it covers a lot of random areas of study.

And i want the shell to be more interactive. So it'll be able to figure out which processes use the screen and which don't. For processes that don't use the screen, harsh will let you know what's going on. That's kind of cool--so you don't get spammed in an emacs session or similar. Mildly important because then you can track events from the shell perspective as opposed to launching a bazillion processes that track stuff in the background.

I want the shell to be running "agents" in the background which could be watching data (watch-dog agents), or collecting data, or even just monitoring background processes.

objectives:

• build a shell that's more interactive
• allow for background tracking of system events through some kind of shell scripting kind of thing
• allow for the possibility of building agents that keep track of and store this information while you're logged in.
• it's called harsh because it's going to backtalk as well. more personality. I always wanted a shell that could talk dirty....

No distributable stuff yet. It's mostly a toy still.