>
> Ok, but looking at the particular case that brought this up I don't
> think it, as an example, does put Linux growth in jeopardy. Saying
> "/bin/sh" is POSIX bourne shell only doesn't stop any advancements for
> those who prefer bash. They can put "#! /bin/bash" on their shell
> scripts to get the extra functionality and not be prevented from using
> its advanced features.
>
> As it is when someone writes a script with "#! /bin/sh" at the top and
> it uses "bash" or "ksh" extensions it's a sort of lie. It's not a bourne
> shell script, it's a bash script. Its not portable, it's not compliant
> and I don't see how it would hurt to actually force these users to put
> "#! /bin/bash" to make it clear that's what the script really is. I
> definitely can't see how it would hold up "growth".
>
I have been caught several times becasuse bash extensions do not work in sh.
I get caught when terminal emulators such as konsole open new windows and use sh
instead of my preferred shell, Fortunately for me I've found how to configure konsole
to do what I want, but the solution is really in the "dreadful hack" class.
I don't know which bash extensions caught me though. Perhaps those who care should
identify errors and take it up with the bash developers.
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
