sed can use any separator instead of / in the s command. Just use something that is not encountered in your paths: s+AAA+BBB+ and so on. Alternatively (and if you don’t want to guess), you can pre-process your path with sed to escape the slashes: pwdesc=$(echo $PWD | sed ‘s_/_\\/_g’) and then do what you … Read more
It does affect, at least bash in my environment, but in very unpleasant way. See these codes. First a.sh: #!/bin/sh echo “First echo” read y echo “$y” echo “That’s all.” b.sh: #!/bin/sh echo “First echo” read y echo “Inserted” echo “$y” # echo “That’s all.” Do $ cp a.sh run.sh $ ./run.sh $ # open … Read more
Use the “dot space script” calling syntax. For example, here’s how to do it using the full path to a script: . /path/to/set_env_vars.sh And here’s how to do it if you’re in the same directory as the script: . set_env_vars.sh These execute the script under the current shell instead of loading another one (which is … Read more
I had this problem in a program I wrote a year ago — turns out the answer is rather complicated. You’ll need to use nohup as well as output redirection, as explained in the wikipedia artcle on nohup, copied here for your convenience. Nohuping backgrounded jobs is for example useful when logged in via SSH, … Read more
There are three approaches to finding the name of the current shell’s executable: Please note that all three approaches can be fooled if the executable of the shell is /bin/sh, but it’s really a renamed bash, for example (which frequently happens). Thus your second question of whether ps output will do is answered with “not … Read more