Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to cat <<EOF >> a file containing code?

I want to print code into a file using cat <<EOF >>:

cat <<EOF >> brightup.sh !/bin/bash curr=`cat /sys/class/backlight/intel_backlight/actual_brightness` if [ $curr -lt 4477 ]; then    curr=$((curr+406));    echo $curr  > /sys/class/backlight/intel_backlight/brightness; fi EOF 

but when I check the file output, I get this:

!/bin/bash curr=1634 if [  -lt 4477 ]; then    curr=406;    echo   > /sys/class/backlight/intel_backlight/brightness; fi 

I tried putting single quotes but the output also carries the single quotes with it. How can I avoid this issue?

like image 844
UberNate Avatar asked Mar 27 '14 19:03

UberNate


People also ask

What does cat << EOF >> mean?

This operator stands for the end of the file. This means that wherever a compiler or an interpreter encounters this operator, it will receive an indication that the file it was reading has ended. Similarly, in bash, the EOF operator is used to specify the end of the file.

What is << EOF called?

In your case, "EOF" is known as a "Here Tag". Basically <<Here tells the shell that you are going to enter a multiline string until the "tag" Here . You can name this tag as you want, it's often EOF or STOP .

How do you echo EOF?

There is no way to echo out an EOF. An EOF can only be generated either by reaching the end of a file or by invoking the keypress bound to the eof terminal setting ( Ctrl D by default) when the file being read is bound to the terminal.


1 Answers

You only need a minimal change; single-quote the here-document delimiter after <<.

cat <<'EOF' >> brightup.sh 

or equivalently backslash-escape it:

cat <<\EOF >>brightup.sh 

Without quoting, the here document will undergo variable substitution, backticks will be evaluated, etc, like you discovered.

If you need to expand some, but not all, values, you need to individually escape the ones you want to prevent.

cat <<EOF >>brightup.sh #!/bin/sh # Created on $(date # : <<-- this will be evaluated before cat;) echo "\$HOME will not be evaluated because it is backslash-escaped" EOF 

will produce

#!/bin/sh # Created on Fri Feb 16 11:00:18 UTC 2018 echo "$HOME will not be evaluated because it is backslash-escaped" 

As suggested by @fedorqui, here is the relevant section from man bash:

Here Documents

This type of redirection instructs the shell to read input from the current source until a line containing only delimiter (with no trailing blanks) is seen. All of the lines read up to that point are then used as the standard input for a command.

The format of here-documents is:

      <<[-]word               here-document       delimiter 

No parameter expansion, command substitution, arithmetic expansion, or pathname expansion is performed on word. If any characters in word are quoted, the delimiter is the result of quote removal on word, and the lines in the here-document are not expanded. If word is unquoted, all lines of the here-document are subjected to parameter expansion, command substitution, and arithmetic expansion. In the latter case, the character sequence \<newline> is ignored, and \ must be used to quote the characters \, $, and `.

like image 168
tripleee Avatar answered Sep 18 '22 07:09

tripleee