Dan Stromberg wrote:
Having a shell function's variable changes reflected in its caller really
kinda makes me shudder - in fact, it reminds me of gosub. It seems like
a bug waiting to happen; I'm amazed I haven't been bitten by it yet.
This is as Posix has standardized: all variables are glo
A simple question and perhaps its simplicity explains why I can't find
an answer elsewhere:
How do I tell bash to kill job 1, rather than pid 1 ?
What does "kill <>" mean? What if there is no jobspec <> and I
type "kill <>" ?
e..g.
$ jobs
[1]+ Stopped blahblahblah
$ ps 1
P
