[prev] [thread] [next] [lurker] [Date index for 2007/01/10]
>
> That's obviously two completely different things there and not a valid
> test at all.
Yep, I just checked and found that a program behaves differently than a built-in
command, and apparently echo is a built-in command. If you think of this as a
feature, that's fine with me, but allow me to disagree. If you think that one
must memorize built-in commands and behaviorial differences between them and
programs, that's also fine, but allow me to disagree again.
Explaining the problem ("echo is a built-in command, an external program would
behave differently") takes about as much space as merely stating that the
solution is "obvious", and some find it more enjoyable.
>
> Please go and read an introduction to unix shells. Heck, it may even
> convince you to dump tcsh if you're lucky.
Too bad the guy who wrote tcsh didn't read an introduction to unix shells. Heck,
it might even convince him to dump the whole project if we were lucky.
As I've said, I use tcsh cause that's what they use around here, and I have to
source (not fork/exec) their scripts. I use Python and avoid *sh for scripting.
Yes, I know bash is considered better for scripting than *csh. Assembler is also
better for scripting than brainfuck.
Do you by any chance have any idea what caused the actual *problem* (timeout
locking etc. etc.)? My current understanding of shells is enough to work around it.
There's stuff above here
Generated at 00:01 on 12 Jan 2007 by mariachi 0.52