I've looked over the scsh docs at various times, though I've never actually used it -- it's never been pre-packaged for distros I've used, and every time I've tried to build it I've run into errors. Perhaps I should try again. As far as the process syntax goes, a little bit of macros over my pipeline library should be able to get you something pretty close. I'll probably do that later.
The parts of scsh aside from the process forms, like the regex stuff, I think are mostly orthogonal to the process stuff, so that could probably just be a different library, then they could be used together.
I just ran across this little thing: https://asciinema.org/a/0utgivr7glk3ssn01fn5uwtey
A lot of that does look pretty good. I think he's probably right that the |> piped output should be the last argument (I've had my `shellify` wrapper making it the first).
I’d love to use a Racket shell and script Unix in a ‘natural’ way.
Not just Unix -- it works on Windows too ;) So is scsh what you consider natural? I definitely want a nice s-expression syntax for it, but also a convenient line-based syntax for interactive use. I like the idea that you can more or less turn a transcript of such commands into a script -- one of the reasons I always encourage people to get used to using a shell is that it makes you think a lot more about automating tasks when you type the same command sequence often. It's something you just can't do with GUI interfaces, and automating boring stuff is one of the joys of programming. Having a nice upgrade path (just gradually put more of it in regular racket until it turns into a "real" program) for those scripts that seem to grow over time is also really appealing to me. Thanks for the feedback. William -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
