In reading some suse startup code (*shiver*),
I came across this construct
func() {
local comm ## command from /proc/$pid/stat
for comm; do
test -s comm || continue
ppid = pidofproc $comm
parents="${parents:+parents:}${ppid}"
done
}
-------------------
Is that valid code? does for have some arcane usage
to test if the contents of it exists as a file or something?
----
Ended up finding that while chasing down a bunch of
lines in the completion.d dir
like
[ $USERLAND = GNU -o $UNAME = Darwin \
-o $UNAME = FreeBSD -o $UNAME = SunOS -o $UNAME = Cygwin \
-o $UNAME = OpenBSD ] &&
man()
}
.....
Which don't work well when some var they expect to be defined,
isn't. Tried telling them to either use [[]] or use quotes, but so far
have been ignored....so having to fix them manually so I don't gets lots of
bogus errors on login and any user-switch (sudo/su)...
