Thank for the answer,
even if I don't think that making available to programmers
a notation which failed to be parsed at export because the
interpreter rely on a specific option disabled by default
is (always ?) a good idea; I'll precise my real use-case:
I wanted to make some functions available o
Raph wrote:
> Hello,
> while trying to export this function :
>
> foo() {
> case "$1" in
> ?(a))
> echo a
> ;;
> esac
> }
>
> with export -f foo I went into some problem
> as soon as any
Hello,
while trying to export this function :
foo() {
case "$1" in
?(a))
echo a
;;
esac
}
with export -f foo I went into some problem
as soon as any new instance is launched :
b