The main flaw of using a here document is that the script’s standard input will be the here document. So if you have a script which wants to process its standard input, python -c is pretty much your only option. On the other hand, using python -c ‘…’ ties up the single-quote for the shell’s … Read more
TAB=”$(printf ‘\t’)” cat > prices.txt << EOF coffee${TAB}\$1.50 tea${TAB}\$1.50 burger${TAB}\$5.00 EOF
This is how I would do it: sudo tee “$OUTFILE” > /dev/null <<‘EOF’ foo bar EOF
Another GNU Make solution. You can do it using the define and export commands as follows: define GITIGNOREDS *.o depend endef SRCS = $(wildcard [a-z]*.c) EXES = $(SRCS:.c=) export GITIGNOREDS .gitignore: $(SRCS) echo $(EXES) | sed ‘s/ /\n/g’ > $@ echo “$$GITIGNOREDS” >> $@ You have to be careful of make expansions (i.e. $(x)) inside … Read more
Chaining commands in a single line You can put the control operator && right after the EOF word in your here document and you can chain more than one command: cat > file <<-EOF && echo -n “hello ” && echo world It will wait for your here-document and then will print hello world. Example … Read more
You can interpolate just like in normal strings <<-TERMINATOR Example #{p[:name]} blah blah blah TERMINATOR
Not as far as I know. The closest I know of is > out.txt ( @echo.bla @echo.bla … ) (@ prevents the command shell itself from printing the commands it’s running, and echo. allows you to start a line with a space.)
(If you are using bash 4, scroll to the end for what I think is the best combination of pure shell and readability.) For heredocs, using tabs is not a matter of preference or style; it’s how the language is defined. usage () { ⟶# Lines between EOF are each indented with the same number … Read more
The way to that would be possible is: printArgs 17 “$(cat <<EOF 18 19 EOF )” But why would you want to use a heredoc for this? heredoc is treated as a file in the arguments so you have to (ab)use cat to get the contents of the file, why not just do something like: … Read more