Pete's Log: shell shell shell

Entry #595, Wed, November 15, 2000, 15:30 EST (Coding, Hacking, & CS stuff)
(posted when I was 22 years old.)
I think OS would have been more fun today if, when Dr Freeh said "I'm gonna wrap this up" he'd meant "wrap" without the 'w'.

So in my continuing quest to break tcsh, I've found a few more interesting things. First of all, doing something like "setenv b c &" doesn't cause b to be set, which makes sense. The odd thing, tho, is that the setenv doesn't terminate until you bring it into the foreground. I don't quite understand what's up with that. I've pretty much come to the conclusion that all my worries about how to handle job control for shell builtins are for naught, since tcsh apparently doesn't concern itself too much with job control for its shell builtins, at least not in the situations in which it'd be difficult. I think I've figured out enough stuff for now, it's time to start coding.

so in other news, malloc is now running setiathome.
Nobody has rated this entry.