## key step: out=$((set -o xtrace;: "$@") 2>&1) # xtrace option shows us quoting for our args ## Cleanup $out # only 1 of the next 4 'left trims' is expected to change $out: out=${out#+++++ } # if $FUNCNAME is eval'd…
I wrote bash function that leverages 'set -x' to get me the quoting in "$@" into a single bash env var say $job or in to a temp file. I use it from time to time -- pretty sure it's not perfect, but it works well enough…
# My Shortlist of News sources ## websites: ## ### <https://projectcensored.org/> ### ### <https://consortiumnews.com> ### ### <https://www.truthdig.com/> ### ### <https://whowhatwhy.org> ### ### <http://accuracy.org/>…
How about a script: a wrapper to run any other script or process, that logs both STDOUT and STDERR in one file, but prepends a short string of your choice for lines that are from STDERR.
## key step: out=$((set -o xtrace;: "$@") 2>&1) # xtrace option shows us quoting for our args ## Cleanup $out # only 1 of the next 4 'left trims' is expected to change $out: out=${out#+++++ } # if $FUNCNAME is eval'd…
I wrote bash function that leverages 'set -x' to get me the quoting in "$@" into a single bash env var say $job or in to a temp file. I use it from time to time -- pretty sure it's not perfect, but it works well enough…
# My Shortlist of News sources ## websites: ## ### <https://projectcensored.org/> ### ### <https://consortiumnews.com> ### ### <https://www.truthdig.com/> ### ### <https://whowhatwhy.org> ### ### <http://accuracy.org/>…
How about a script: a wrapper to run any other script or process, that logs both STDOUT and STDERR in one file, but prepends a short string of your choice for lines that are from STDERR.