If it was the exit code and not the result, you could just use if func arg; then … If you cannot make the function return a proper exit code (with return N), and you have to use string results, use Alex Gitelman’s answer. $ help if: if: if COMMANDS; then COMMANDS; [ elif COMMANDS; … Read more
Have you considered using GitPython? It’s designed to handle all this nonsense for you. import git g = git.cmd.Git(git_dir) g.pull() https://github.com/gitpython-developers/GitPython
a=(foo bar “foo 1” “bar two”) #create an array b=(“${a[@]}”) #copy the array in another one for value in “${b[@]}” ; do #print the new array echo “$value” done
The accepted answer explains how to do this for all files (use files.eol in settings), but if you ever need to override that setting there’s an indicator at the bottom right that you can click on and change for this one file. Took me a while to notice that this was clickable.
Pure Bash, no external utilities This demonstration does full justification, but you can just omit subtracting the length of the second string if you want ragged-right lines. pad=$(printf ‘%0.1s’ “-“{1..60}) padlength=40 string2=’bbbbbbb’ for string1 in a aa aaaa aaaaaaaa do printf ‘%s’ “$string1” printf ‘%*.*s’ 0 $((padlength – ${#string1} – ${#string2} )) “$pad” printf ‘%s\n’ … Read more
sending the signal 0 to a given PID just checks if any process with the given PID is running and you have the permission to send a signal to it. For more information see the following manpages: kill(1) $ man 1 kill … If sig is 0, then no signal is sent, but error checking … Read more
The mktemp(1) man page explains it fairly well: Traditionally, many shell scripts take the name of the program with the pid as a suffix and use that as a temporary file name. This kind of naming scheme is predictable and the race condition it creates is easy for an attacker to win. A safer, though … Read more
You can use the -i flag which makes your pattern case insensitive: grep -iF “success…” file1 Also, there is no need for cat. grep takes a file with the syntax grep <pattern> <file>. I also used the -F flag to search for a fixed string to avoid escaping the ellipsis.
To view all env variables: docker exec container env To get one: docker exec container env | grep VARIABLE | cut -d’=’ -f2
Try this Bash syntax instead of trying to use an external program expr: count=$((FIRSTV-SECONDV)) BTW, the correct syntax of using expr is: count=$(expr $FIRSTV – $SECONDV) But keep in mind using expr is going to be slower than the internal Bash syntax I provided above.