Append to files Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election Results Why I closed the “Why is Kali so hard” questionWhy is looping over find's output bad practice?Have backticks (i.e. `cmd`) in *sh shells been deprecated?How do I append text to the beginning and end of multiple text files in Bash?sed insert in the beginning of multiple files is not workingHow to pass an argument from a bash script to 'x-terminal-emulator -e bash -c'?How to append extension to files with certain filename formatFind files and recursively append text to themsed backreference: get each line and append it to end of linesed append a text with many lines after matching of multiple strings while the text remains many lines in sed commandHow to copy strings from middle of lines (between strings) to the end of linesFind words after specific symbol on lineHow to sed chunks text from a stream of files from find

Generate an RGB colour grid

T-test, ANOVA or Regression, what's the difference?

Is there such thing as an Availability Group failover trigger?

Using audio cues to encourage good posture

Why are std::future and std::promise not final?

How come Sam didn't become Lord of Horn Hill?

How can I use the Python library networkx from Mathematica?

Circuit to "zoom in" on mV fluctuations of a DC signal?

For a new assistant professor in CS, how to build/manage a publication pipeline

Is there a kind of relay only consumes power when switching?

Is it cost-effective to upgrade an old-ish Giant Escape R3 commuter bike with entry-level branded parts (wheels, drivetrain)?

Why do we bend a book to keep it straight?

Amount of permutations on an NxNxN Rubik's Cube

How to tell that you are a giant?

Novel: non-telepath helps overthrow rule by telepaths

Denied boarding although I have proper visa and documentation. To whom should I make a complaint?

8 Prisoners wearing hats

Find the length x such that the two distances in the triangle are the same

Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?

When a candle burns, why does the top of wick glow if bottom of flame is hottest?

What is this building called? (It was built in 2002)

What do you call the main part of a joke?

What is homebrew?

Do square wave exist?



Append to files



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionWhy is looping over find's output bad practice?Have backticks (i.e. `cmd`) in *sh shells been deprecated?How do I append text to the beginning and end of multiple text files in Bash?sed insert in the beginning of multiple files is not workingHow to pass an argument from a bash script to 'x-terminal-emulator -e bash -c'?How to append extension to files with certain filename formatFind files and recursively append text to themsed backreference: get each line and append it to end of linesed append a text with many lines after matching of multiple strings while the text remains many lines in sed commandHow to copy strings from middle of lines (between strings) to the end of linesFind words after specific symbol on lineHow to sed chunks text from a stream of files from find



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








3















I have a directory full of files. My goal is to append text to the beginning of the file. The text that goes at the beginning is the same for each file.
This is my attempt



#!/bin/bash 

for file in `find . -type f -executable`;do
sed '/#!/bin/bash/a Hello Word'


done


My script does nothing but crash










share|improve this question



















  • 2





    Have a look at this question. Looping over find's output is a bad practice.

    – Iñaki Murillo
    Nov 10 '16 at 8:41

















3















I have a directory full of files. My goal is to append text to the beginning of the file. The text that goes at the beginning is the same for each file.
This is my attempt



#!/bin/bash 

for file in `find . -type f -executable`;do
sed '/#!/bin/bash/a Hello Word'


done


My script does nothing but crash










share|improve this question



















  • 2





    Have a look at this question. Looping over find's output is a bad practice.

    – Iñaki Murillo
    Nov 10 '16 at 8:41













3












3








3








I have a directory full of files. My goal is to append text to the beginning of the file. The text that goes at the beginning is the same for each file.
This is my attempt



#!/bin/bash 

for file in `find . -type f -executable`;do
sed '/#!/bin/bash/a Hello Word'


done


My script does nothing but crash










share|improve this question
















I have a directory full of files. My goal is to append text to the beginning of the file. The text that goes at the beginning is the same for each file.
This is my attempt



#!/bin/bash 

for file in `find . -type f -executable`;do
sed '/#!/bin/bash/a Hello Word'


done


My script does nothing but crash







shell-script files sed find






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 13 at 15:04









Rui F Ribeiro

42.1k1484142




42.1k1484142










asked Nov 10 '16 at 8:20









K.UK.U

205




205







  • 2





    Have a look at this question. Looping over find's output is a bad practice.

    – Iñaki Murillo
    Nov 10 '16 at 8:41












  • 2





    Have a look at this question. Looping over find's output is a bad practice.

    – Iñaki Murillo
    Nov 10 '16 at 8:41







2




2





Have a look at this question. Looping over find's output is a bad practice.

– Iñaki Murillo
Nov 10 '16 at 8:41





Have a look at this question. Looping over find's output is a bad practice.

– Iñaki Murillo
Nov 10 '16 at 8:41










3 Answers
3






active

oldest

votes


















5















#!/bin/bash

for file in `find . -type f -executable`;do
sed '/#!/bin/bash/a Hello Word'
fi

done



This script has a great number of problems.




First, it's not a valid Bash script, because you have fi with no corresponding if.




Stylistically (after removing the fi line), I would remove the empty line before done and add a space before do. But that's relatively trivial.




Now, as to best practices, you are using backticks for command substitution rather than the recommended modern form, $(...). Backticks are supported purely for historical reasons and are not recommended for any new scripts; see:



  • Have backticks (i.e. `cmd`) in *sh shells been deprecated?


You have a robustness issue in that you are looping over the output of find—a very bad idea, and totally unnecessary. Your script will break on any filenames containing whitespace or special characters. See:




  • Why is looping over find's output bad practice?)


If you want your script to be portable, you should stick to POSIX specified features whenever possible. In particular the -executable primary to find is not specified by POSIX. Consider using -perm +700 instead.



Also in the realm of portability, using the "append" command to Sed (a) without a following <newline> sequence works in GNU Sed, but is not standard.




You set the file variable in your for loop to the name of each file in turn (assuming no special characters or whitespace in the filenames, which will cause the file variable to contain something which is not a filename), but you never actually use the file variable.



Your Sed command is not given any file to run on, so it will attempt to run on standard input. Thus when you run the script it will simply wait for input.




Your Sed script itself is incorrect, independent of the fact that it's missing a filename to operate on.



If you use / as a delimiter for a regex (which is most usual), you need to backslash-escape all instances of / which occur within the regex. The only portion of your command which will be read as a regex is /#!/, and the rest (starting with bin) will be interpreted as a Sed command.



Instead, the usual solution would be to replace each / other than the final regex delimiter with /. (I see that you escaped only the last slash, which should not be escaped.)



There is a little-known feature in Sed, which you could use to your advantage here. Any character (other than a backslash or newline) can be used as a regex delimiter, rather than only using a slash. So rather than using /#!/bin/bash/ as a Sed address, you could use the equivalent :#!/bin/bash:




Now if you've handled all of the above points, you will have a working script. It may not do what you want it to do, but it will actually do something. Such a script would look like this:



#!/bin/bash

find . -type f -perm -700 -exec sed ':#!/bin/bash:a
Hello World' +


What does this script do? It searches the current directory recursively for all files with the executable bit set (for the owner), and for each such file, prints the entire file with the text Hello World appended after any lines which contain the text #!/bin/bash.



Sed is not actually designed for editing files in place; it is the Stream EDitor. GNU Sed will allow you to edit files in place using the -i switch, but I would just use the standard tool ex for file editing.




But there is another point here. If you want to add the line Hello World in a Bash script, it won't actually do anything, as Hello is not a valid command name. Perhaps what you want is to print the text "Hello World" in the Bash script, in other words to add echo "Hello World, which could make sense.



Now we're into the realm of clarifying more exactly what your script is supposed to do.




The Final Script



So my more exact statement of the specifications for this script are:



  • The script shall find all regular files in the current directory (or any subdirectory recursively) which have the executable bit set for the owner.

  • For each such file, the script shall check whether the first line of the file exactly equals the string #!/bin/bash.

  • Only for files with this exact first line, the script shall insert the exact text echo "Hello World", followed by a newline character, after the first line of the file. (This change shall be saved to the file, not printed to standard out.)

Here is a script matching those exact specifications, using only POSIX tools and features:



#!/bin/sh

find . -type f -perm -700 -exec sh -c '
for f
do
head -n 1 "$f" | grep -qFx "#!/bin/bash" &&
printf "%sn" "1a" "echo "Hello World"" . x | ex "$f"
done
' find-sh +





share|improve this answer

























  • Hi, when I run this script I got : find: invalid mode ‘+700’

    – K.U
    Nov 10 '16 at 23:26











  • I'm using Virtual Machine on MacOs and the version is 4.4.0-45-generic I think.

    – K.U
    Nov 10 '16 at 23:43











  • Even it prints out that error the code still append : echo "Hello World" to my executable files

    – K.U
    Nov 10 '16 at 23:48











  • @K.U, fixed. Use -700, not +700.

    – Wildcard
    Nov 11 '16 at 0:04











  • it appends "echo "Hello World" " instead of just "Hello World". Should I remove one of the " "

    – K.U
    Nov 11 '16 at 0:10


















0














what you are trying to achieve ? to find out the executable scripts, use the below command



find . -type f -perm /u+x,g+x,o+x | while read file
do
filename=$(echo $file | awk -F/ 'print $NF')
echo "File Name : $filename"
done


If you are trying append Hello World after the shebang line, then your sed command should be



 sed '/#!/bin/bash/a Hello Word' $file


if you want to make the changes in the file itself, then add -i in sed command






share|improve this answer

























  • Hi, I'm trying to append Hello World to executable files in a directory. I know how to find executable files, but I don't quite know how I could append text to those file

    – K.U
    Nov 10 '16 at 23:33











  • When I run your code to find executables file I got: File Name : ./insert.sh Is there a way I can only get: File Name : insert.sh

    – K.U
    Nov 10 '16 at 23:39












  • modified the answer

    – Kamaraj
    Nov 11 '16 at 3:35


















-2














find . -type f -executable -exec sed '/^#!/bin/bash/a Hello World' ;






share|improve this answer























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f322255%2fappend-to-files%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    5















    #!/bin/bash

    for file in `find . -type f -executable`;do
    sed '/#!/bin/bash/a Hello Word'
    fi

    done



    This script has a great number of problems.




    First, it's not a valid Bash script, because you have fi with no corresponding if.




    Stylistically (after removing the fi line), I would remove the empty line before done and add a space before do. But that's relatively trivial.




    Now, as to best practices, you are using backticks for command substitution rather than the recommended modern form, $(...). Backticks are supported purely for historical reasons and are not recommended for any new scripts; see:



    • Have backticks (i.e. `cmd`) in *sh shells been deprecated?


    You have a robustness issue in that you are looping over the output of find—a very bad idea, and totally unnecessary. Your script will break on any filenames containing whitespace or special characters. See:




    • Why is looping over find's output bad practice?)


    If you want your script to be portable, you should stick to POSIX specified features whenever possible. In particular the -executable primary to find is not specified by POSIX. Consider using -perm +700 instead.



    Also in the realm of portability, using the "append" command to Sed (a) without a following <newline> sequence works in GNU Sed, but is not standard.




    You set the file variable in your for loop to the name of each file in turn (assuming no special characters or whitespace in the filenames, which will cause the file variable to contain something which is not a filename), but you never actually use the file variable.



    Your Sed command is not given any file to run on, so it will attempt to run on standard input. Thus when you run the script it will simply wait for input.




    Your Sed script itself is incorrect, independent of the fact that it's missing a filename to operate on.



    If you use / as a delimiter for a regex (which is most usual), you need to backslash-escape all instances of / which occur within the regex. The only portion of your command which will be read as a regex is /#!/, and the rest (starting with bin) will be interpreted as a Sed command.



    Instead, the usual solution would be to replace each / other than the final regex delimiter with /. (I see that you escaped only the last slash, which should not be escaped.)



    There is a little-known feature in Sed, which you could use to your advantage here. Any character (other than a backslash or newline) can be used as a regex delimiter, rather than only using a slash. So rather than using /#!/bin/bash/ as a Sed address, you could use the equivalent :#!/bin/bash:




    Now if you've handled all of the above points, you will have a working script. It may not do what you want it to do, but it will actually do something. Such a script would look like this:



    #!/bin/bash

    find . -type f -perm -700 -exec sed ':#!/bin/bash:a
    Hello World' +


    What does this script do? It searches the current directory recursively for all files with the executable bit set (for the owner), and for each such file, prints the entire file with the text Hello World appended after any lines which contain the text #!/bin/bash.



    Sed is not actually designed for editing files in place; it is the Stream EDitor. GNU Sed will allow you to edit files in place using the -i switch, but I would just use the standard tool ex for file editing.




    But there is another point here. If you want to add the line Hello World in a Bash script, it won't actually do anything, as Hello is not a valid command name. Perhaps what you want is to print the text "Hello World" in the Bash script, in other words to add echo "Hello World, which could make sense.



    Now we're into the realm of clarifying more exactly what your script is supposed to do.




    The Final Script



    So my more exact statement of the specifications for this script are:



    • The script shall find all regular files in the current directory (or any subdirectory recursively) which have the executable bit set for the owner.

    • For each such file, the script shall check whether the first line of the file exactly equals the string #!/bin/bash.

    • Only for files with this exact first line, the script shall insert the exact text echo "Hello World", followed by a newline character, after the first line of the file. (This change shall be saved to the file, not printed to standard out.)

    Here is a script matching those exact specifications, using only POSIX tools and features:



    #!/bin/sh

    find . -type f -perm -700 -exec sh -c '
    for f
    do
    head -n 1 "$f" | grep -qFx "#!/bin/bash" &&
    printf "%sn" "1a" "echo "Hello World"" . x | ex "$f"
    done
    ' find-sh +





    share|improve this answer

























    • Hi, when I run this script I got : find: invalid mode ‘+700’

      – K.U
      Nov 10 '16 at 23:26











    • I'm using Virtual Machine on MacOs and the version is 4.4.0-45-generic I think.

      – K.U
      Nov 10 '16 at 23:43











    • Even it prints out that error the code still append : echo "Hello World" to my executable files

      – K.U
      Nov 10 '16 at 23:48











    • @K.U, fixed. Use -700, not +700.

      – Wildcard
      Nov 11 '16 at 0:04











    • it appends "echo "Hello World" " instead of just "Hello World". Should I remove one of the " "

      – K.U
      Nov 11 '16 at 0:10















    5















    #!/bin/bash

    for file in `find . -type f -executable`;do
    sed '/#!/bin/bash/a Hello Word'
    fi

    done



    This script has a great number of problems.




    First, it's not a valid Bash script, because you have fi with no corresponding if.




    Stylistically (after removing the fi line), I would remove the empty line before done and add a space before do. But that's relatively trivial.




    Now, as to best practices, you are using backticks for command substitution rather than the recommended modern form, $(...). Backticks are supported purely for historical reasons and are not recommended for any new scripts; see:



    • Have backticks (i.e. `cmd`) in *sh shells been deprecated?


    You have a robustness issue in that you are looping over the output of find—a very bad idea, and totally unnecessary. Your script will break on any filenames containing whitespace or special characters. See:




    • Why is looping over find's output bad practice?)


    If you want your script to be portable, you should stick to POSIX specified features whenever possible. In particular the -executable primary to find is not specified by POSIX. Consider using -perm +700 instead.



    Also in the realm of portability, using the "append" command to Sed (a) without a following <newline> sequence works in GNU Sed, but is not standard.




    You set the file variable in your for loop to the name of each file in turn (assuming no special characters or whitespace in the filenames, which will cause the file variable to contain something which is not a filename), but you never actually use the file variable.



    Your Sed command is not given any file to run on, so it will attempt to run on standard input. Thus when you run the script it will simply wait for input.




    Your Sed script itself is incorrect, independent of the fact that it's missing a filename to operate on.



    If you use / as a delimiter for a regex (which is most usual), you need to backslash-escape all instances of / which occur within the regex. The only portion of your command which will be read as a regex is /#!/, and the rest (starting with bin) will be interpreted as a Sed command.



    Instead, the usual solution would be to replace each / other than the final regex delimiter with /. (I see that you escaped only the last slash, which should not be escaped.)



    There is a little-known feature in Sed, which you could use to your advantage here. Any character (other than a backslash or newline) can be used as a regex delimiter, rather than only using a slash. So rather than using /#!/bin/bash/ as a Sed address, you could use the equivalent :#!/bin/bash:




    Now if you've handled all of the above points, you will have a working script. It may not do what you want it to do, but it will actually do something. Such a script would look like this:



    #!/bin/bash

    find . -type f -perm -700 -exec sed ':#!/bin/bash:a
    Hello World' +


    What does this script do? It searches the current directory recursively for all files with the executable bit set (for the owner), and for each such file, prints the entire file with the text Hello World appended after any lines which contain the text #!/bin/bash.



    Sed is not actually designed for editing files in place; it is the Stream EDitor. GNU Sed will allow you to edit files in place using the -i switch, but I would just use the standard tool ex for file editing.




    But there is another point here. If you want to add the line Hello World in a Bash script, it won't actually do anything, as Hello is not a valid command name. Perhaps what you want is to print the text "Hello World" in the Bash script, in other words to add echo "Hello World, which could make sense.



    Now we're into the realm of clarifying more exactly what your script is supposed to do.




    The Final Script



    So my more exact statement of the specifications for this script are:



    • The script shall find all regular files in the current directory (or any subdirectory recursively) which have the executable bit set for the owner.

    • For each such file, the script shall check whether the first line of the file exactly equals the string #!/bin/bash.

    • Only for files with this exact first line, the script shall insert the exact text echo "Hello World", followed by a newline character, after the first line of the file. (This change shall be saved to the file, not printed to standard out.)

    Here is a script matching those exact specifications, using only POSIX tools and features:



    #!/bin/sh

    find . -type f -perm -700 -exec sh -c '
    for f
    do
    head -n 1 "$f" | grep -qFx "#!/bin/bash" &&
    printf "%sn" "1a" "echo "Hello World"" . x | ex "$f"
    done
    ' find-sh +





    share|improve this answer

























    • Hi, when I run this script I got : find: invalid mode ‘+700’

      – K.U
      Nov 10 '16 at 23:26











    • I'm using Virtual Machine on MacOs and the version is 4.4.0-45-generic I think.

      – K.U
      Nov 10 '16 at 23:43











    • Even it prints out that error the code still append : echo "Hello World" to my executable files

      – K.U
      Nov 10 '16 at 23:48











    • @K.U, fixed. Use -700, not +700.

      – Wildcard
      Nov 11 '16 at 0:04











    • it appends "echo "Hello World" " instead of just "Hello World". Should I remove one of the " "

      – K.U
      Nov 11 '16 at 0:10













    5












    5








    5








    #!/bin/bash

    for file in `find . -type f -executable`;do
    sed '/#!/bin/bash/a Hello Word'
    fi

    done



    This script has a great number of problems.




    First, it's not a valid Bash script, because you have fi with no corresponding if.




    Stylistically (after removing the fi line), I would remove the empty line before done and add a space before do. But that's relatively trivial.




    Now, as to best practices, you are using backticks for command substitution rather than the recommended modern form, $(...). Backticks are supported purely for historical reasons and are not recommended for any new scripts; see:



    • Have backticks (i.e. `cmd`) in *sh shells been deprecated?


    You have a robustness issue in that you are looping over the output of find—a very bad idea, and totally unnecessary. Your script will break on any filenames containing whitespace or special characters. See:




    • Why is looping over find's output bad practice?)


    If you want your script to be portable, you should stick to POSIX specified features whenever possible. In particular the -executable primary to find is not specified by POSIX. Consider using -perm +700 instead.



    Also in the realm of portability, using the "append" command to Sed (a) without a following <newline> sequence works in GNU Sed, but is not standard.




    You set the file variable in your for loop to the name of each file in turn (assuming no special characters or whitespace in the filenames, which will cause the file variable to contain something which is not a filename), but you never actually use the file variable.



    Your Sed command is not given any file to run on, so it will attempt to run on standard input. Thus when you run the script it will simply wait for input.




    Your Sed script itself is incorrect, independent of the fact that it's missing a filename to operate on.



    If you use / as a delimiter for a regex (which is most usual), you need to backslash-escape all instances of / which occur within the regex. The only portion of your command which will be read as a regex is /#!/, and the rest (starting with bin) will be interpreted as a Sed command.



    Instead, the usual solution would be to replace each / other than the final regex delimiter with /. (I see that you escaped only the last slash, which should not be escaped.)



    There is a little-known feature in Sed, which you could use to your advantage here. Any character (other than a backslash or newline) can be used as a regex delimiter, rather than only using a slash. So rather than using /#!/bin/bash/ as a Sed address, you could use the equivalent :#!/bin/bash:




    Now if you've handled all of the above points, you will have a working script. It may not do what you want it to do, but it will actually do something. Such a script would look like this:



    #!/bin/bash

    find . -type f -perm -700 -exec sed ':#!/bin/bash:a
    Hello World' +


    What does this script do? It searches the current directory recursively for all files with the executable bit set (for the owner), and for each such file, prints the entire file with the text Hello World appended after any lines which contain the text #!/bin/bash.



    Sed is not actually designed for editing files in place; it is the Stream EDitor. GNU Sed will allow you to edit files in place using the -i switch, but I would just use the standard tool ex for file editing.




    But there is another point here. If you want to add the line Hello World in a Bash script, it won't actually do anything, as Hello is not a valid command name. Perhaps what you want is to print the text "Hello World" in the Bash script, in other words to add echo "Hello World, which could make sense.



    Now we're into the realm of clarifying more exactly what your script is supposed to do.




    The Final Script



    So my more exact statement of the specifications for this script are:



    • The script shall find all regular files in the current directory (or any subdirectory recursively) which have the executable bit set for the owner.

    • For each such file, the script shall check whether the first line of the file exactly equals the string #!/bin/bash.

    • Only for files with this exact first line, the script shall insert the exact text echo "Hello World", followed by a newline character, after the first line of the file. (This change shall be saved to the file, not printed to standard out.)

    Here is a script matching those exact specifications, using only POSIX tools and features:



    #!/bin/sh

    find . -type f -perm -700 -exec sh -c '
    for f
    do
    head -n 1 "$f" | grep -qFx "#!/bin/bash" &&
    printf "%sn" "1a" "echo "Hello World"" . x | ex "$f"
    done
    ' find-sh +





    share|improve this answer
















    #!/bin/bash

    for file in `find . -type f -executable`;do
    sed '/#!/bin/bash/a Hello Word'
    fi

    done



    This script has a great number of problems.




    First, it's not a valid Bash script, because you have fi with no corresponding if.




    Stylistically (after removing the fi line), I would remove the empty line before done and add a space before do. But that's relatively trivial.




    Now, as to best practices, you are using backticks for command substitution rather than the recommended modern form, $(...). Backticks are supported purely for historical reasons and are not recommended for any new scripts; see:



    • Have backticks (i.e. `cmd`) in *sh shells been deprecated?


    You have a robustness issue in that you are looping over the output of find—a very bad idea, and totally unnecessary. Your script will break on any filenames containing whitespace or special characters. See:




    • Why is looping over find's output bad practice?)


    If you want your script to be portable, you should stick to POSIX specified features whenever possible. In particular the -executable primary to find is not specified by POSIX. Consider using -perm +700 instead.



    Also in the realm of portability, using the "append" command to Sed (a) without a following <newline> sequence works in GNU Sed, but is not standard.




    You set the file variable in your for loop to the name of each file in turn (assuming no special characters or whitespace in the filenames, which will cause the file variable to contain something which is not a filename), but you never actually use the file variable.



    Your Sed command is not given any file to run on, so it will attempt to run on standard input. Thus when you run the script it will simply wait for input.




    Your Sed script itself is incorrect, independent of the fact that it's missing a filename to operate on.



    If you use / as a delimiter for a regex (which is most usual), you need to backslash-escape all instances of / which occur within the regex. The only portion of your command which will be read as a regex is /#!/, and the rest (starting with bin) will be interpreted as a Sed command.



    Instead, the usual solution would be to replace each / other than the final regex delimiter with /. (I see that you escaped only the last slash, which should not be escaped.)



    There is a little-known feature in Sed, which you could use to your advantage here. Any character (other than a backslash or newline) can be used as a regex delimiter, rather than only using a slash. So rather than using /#!/bin/bash/ as a Sed address, you could use the equivalent :#!/bin/bash:




    Now if you've handled all of the above points, you will have a working script. It may not do what you want it to do, but it will actually do something. Such a script would look like this:



    #!/bin/bash

    find . -type f -perm -700 -exec sed ':#!/bin/bash:a
    Hello World' +


    What does this script do? It searches the current directory recursively for all files with the executable bit set (for the owner), and for each such file, prints the entire file with the text Hello World appended after any lines which contain the text #!/bin/bash.



    Sed is not actually designed for editing files in place; it is the Stream EDitor. GNU Sed will allow you to edit files in place using the -i switch, but I would just use the standard tool ex for file editing.




    But there is another point here. If you want to add the line Hello World in a Bash script, it won't actually do anything, as Hello is not a valid command name. Perhaps what you want is to print the text "Hello World" in the Bash script, in other words to add echo "Hello World, which could make sense.



    Now we're into the realm of clarifying more exactly what your script is supposed to do.




    The Final Script



    So my more exact statement of the specifications for this script are:



    • The script shall find all regular files in the current directory (or any subdirectory recursively) which have the executable bit set for the owner.

    • For each such file, the script shall check whether the first line of the file exactly equals the string #!/bin/bash.

    • Only for files with this exact first line, the script shall insert the exact text echo "Hello World", followed by a newline character, after the first line of the file. (This change shall be saved to the file, not printed to standard out.)

    Here is a script matching those exact specifications, using only POSIX tools and features:



    #!/bin/sh

    find . -type f -perm -700 -exec sh -c '
    for f
    do
    head -n 1 "$f" | grep -qFx "#!/bin/bash" &&
    printf "%sn" "1a" "echo "Hello World"" . x | ex "$f"
    done
    ' find-sh +






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Apr 13 '17 at 12:37









    Community

    1




    1










    answered Nov 10 '16 at 10:13









    WildcardWildcard

    23.3k1067172




    23.3k1067172












    • Hi, when I run this script I got : find: invalid mode ‘+700’

      – K.U
      Nov 10 '16 at 23:26











    • I'm using Virtual Machine on MacOs and the version is 4.4.0-45-generic I think.

      – K.U
      Nov 10 '16 at 23:43











    • Even it prints out that error the code still append : echo "Hello World" to my executable files

      – K.U
      Nov 10 '16 at 23:48











    • @K.U, fixed. Use -700, not +700.

      – Wildcard
      Nov 11 '16 at 0:04











    • it appends "echo "Hello World" " instead of just "Hello World". Should I remove one of the " "

      – K.U
      Nov 11 '16 at 0:10

















    • Hi, when I run this script I got : find: invalid mode ‘+700’

      – K.U
      Nov 10 '16 at 23:26











    • I'm using Virtual Machine on MacOs and the version is 4.4.0-45-generic I think.

      – K.U
      Nov 10 '16 at 23:43











    • Even it prints out that error the code still append : echo "Hello World" to my executable files

      – K.U
      Nov 10 '16 at 23:48











    • @K.U, fixed. Use -700, not +700.

      – Wildcard
      Nov 11 '16 at 0:04











    • it appends "echo "Hello World" " instead of just "Hello World". Should I remove one of the " "

      – K.U
      Nov 11 '16 at 0:10
















    Hi, when I run this script I got : find: invalid mode ‘+700’

    – K.U
    Nov 10 '16 at 23:26





    Hi, when I run this script I got : find: invalid mode ‘+700’

    – K.U
    Nov 10 '16 at 23:26













    I'm using Virtual Machine on MacOs and the version is 4.4.0-45-generic I think.

    – K.U
    Nov 10 '16 at 23:43





    I'm using Virtual Machine on MacOs and the version is 4.4.0-45-generic I think.

    – K.U
    Nov 10 '16 at 23:43













    Even it prints out that error the code still append : echo "Hello World" to my executable files

    – K.U
    Nov 10 '16 at 23:48





    Even it prints out that error the code still append : echo "Hello World" to my executable files

    – K.U
    Nov 10 '16 at 23:48













    @K.U, fixed. Use -700, not +700.

    – Wildcard
    Nov 11 '16 at 0:04





    @K.U, fixed. Use -700, not +700.

    – Wildcard
    Nov 11 '16 at 0:04













    it appends "echo "Hello World" " instead of just "Hello World". Should I remove one of the " "

    – K.U
    Nov 11 '16 at 0:10





    it appends "echo "Hello World" " instead of just "Hello World". Should I remove one of the " "

    – K.U
    Nov 11 '16 at 0:10













    0














    what you are trying to achieve ? to find out the executable scripts, use the below command



    find . -type f -perm /u+x,g+x,o+x | while read file
    do
    filename=$(echo $file | awk -F/ 'print $NF')
    echo "File Name : $filename"
    done


    If you are trying append Hello World after the shebang line, then your sed command should be



     sed '/#!/bin/bash/a Hello Word' $file


    if you want to make the changes in the file itself, then add -i in sed command






    share|improve this answer

























    • Hi, I'm trying to append Hello World to executable files in a directory. I know how to find executable files, but I don't quite know how I could append text to those file

      – K.U
      Nov 10 '16 at 23:33











    • When I run your code to find executables file I got: File Name : ./insert.sh Is there a way I can only get: File Name : insert.sh

      – K.U
      Nov 10 '16 at 23:39












    • modified the answer

      – Kamaraj
      Nov 11 '16 at 3:35















    0














    what you are trying to achieve ? to find out the executable scripts, use the below command



    find . -type f -perm /u+x,g+x,o+x | while read file
    do
    filename=$(echo $file | awk -F/ 'print $NF')
    echo "File Name : $filename"
    done


    If you are trying append Hello World after the shebang line, then your sed command should be



     sed '/#!/bin/bash/a Hello Word' $file


    if you want to make the changes in the file itself, then add -i in sed command






    share|improve this answer

























    • Hi, I'm trying to append Hello World to executable files in a directory. I know how to find executable files, but I don't quite know how I could append text to those file

      – K.U
      Nov 10 '16 at 23:33











    • When I run your code to find executables file I got: File Name : ./insert.sh Is there a way I can only get: File Name : insert.sh

      – K.U
      Nov 10 '16 at 23:39












    • modified the answer

      – Kamaraj
      Nov 11 '16 at 3:35













    0












    0








    0







    what you are trying to achieve ? to find out the executable scripts, use the below command



    find . -type f -perm /u+x,g+x,o+x | while read file
    do
    filename=$(echo $file | awk -F/ 'print $NF')
    echo "File Name : $filename"
    done


    If you are trying append Hello World after the shebang line, then your sed command should be



     sed '/#!/bin/bash/a Hello Word' $file


    if you want to make the changes in the file itself, then add -i in sed command






    share|improve this answer















    what you are trying to achieve ? to find out the executable scripts, use the below command



    find . -type f -perm /u+x,g+x,o+x | while read file
    do
    filename=$(echo $file | awk -F/ 'print $NF')
    echo "File Name : $filename"
    done


    If you are trying append Hello World after the shebang line, then your sed command should be



     sed '/#!/bin/bash/a Hello Word' $file


    if you want to make the changes in the file itself, then add -i in sed command







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Nov 11 '16 at 3:35

























    answered Nov 10 '16 at 8:33









    KamarajKamaraj

    2,9991514




    2,9991514












    • Hi, I'm trying to append Hello World to executable files in a directory. I know how to find executable files, but I don't quite know how I could append text to those file

      – K.U
      Nov 10 '16 at 23:33











    • When I run your code to find executables file I got: File Name : ./insert.sh Is there a way I can only get: File Name : insert.sh

      – K.U
      Nov 10 '16 at 23:39












    • modified the answer

      – Kamaraj
      Nov 11 '16 at 3:35

















    • Hi, I'm trying to append Hello World to executable files in a directory. I know how to find executable files, but I don't quite know how I could append text to those file

      – K.U
      Nov 10 '16 at 23:33











    • When I run your code to find executables file I got: File Name : ./insert.sh Is there a way I can only get: File Name : insert.sh

      – K.U
      Nov 10 '16 at 23:39












    • modified the answer

      – Kamaraj
      Nov 11 '16 at 3:35
















    Hi, I'm trying to append Hello World to executable files in a directory. I know how to find executable files, but I don't quite know how I could append text to those file

    – K.U
    Nov 10 '16 at 23:33





    Hi, I'm trying to append Hello World to executable files in a directory. I know how to find executable files, but I don't quite know how I could append text to those file

    – K.U
    Nov 10 '16 at 23:33













    When I run your code to find executables file I got: File Name : ./insert.sh Is there a way I can only get: File Name : insert.sh

    – K.U
    Nov 10 '16 at 23:39






    When I run your code to find executables file I got: File Name : ./insert.sh Is there a way I can only get: File Name : insert.sh

    – K.U
    Nov 10 '16 at 23:39














    modified the answer

    – Kamaraj
    Nov 11 '16 at 3:35





    modified the answer

    – Kamaraj
    Nov 11 '16 at 3:35











    -2














    find . -type f -executable -exec sed '/^#!/bin/bash/a Hello World' ;






    share|improve this answer



























      -2














      find . -type f -executable -exec sed '/^#!/bin/bash/a Hello World' ;






      share|improve this answer

























        -2












        -2








        -2







        find . -type f -executable -exec sed '/^#!/bin/bash/a Hello World' ;






        share|improve this answer













        find . -type f -executable -exec sed '/^#!/bin/bash/a Hello World' ;







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 10 '16 at 9:59









        ewattewatt

        37028




        37028



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f322255%2fappend-to-files%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Àrd-bhaile Cathair chruinne/Baile mòr cruinne | Artagailean ceangailte | Clàr-taice na seòladaireachd

            대한민국 목차 국명 지리 역사 정치 국방 경제 사회 문화 국제 순위 관련 항목 각주 외부 링크 둘러보기 메뉴북위 37° 34′ 08″ 동경 126° 58′ 36″ / 북위 37.568889° 동경 126.976667°  / 37.568889; 126.976667ehThe Korean Repository문단을 편집문단을 편집추가해Clarkson PLC 사Report for Selected Countries and Subjects-Korea“Human Development Index and its components: P.198”“http://www.law.go.kr/%EB%B2%95%EB%A0%B9/%EB%8C%80%ED%95%9C%EB%AF%BC%EA%B5%AD%EA%B5%AD%EA%B8%B0%EB%B2%95”"한국은 국제법상 한반도 유일 합법정부 아니다" - 오마이뉴스 모바일Report for Selected Countries and Subjects: South Korea격동의 역사와 함께한 조선일보 90년 : 조선일보 인수해 혁신시킨 신석우, 임시정부 때는 '대한민국' 국호(國號) 정해《우리가 몰랐던 우리 역사: 나라 이름의 비밀을 찾아가는 역사 여행》“남북 공식호칭 ‘남한’‘북한’으로 쓴다”“Corea 대 Korea, 누가 이긴 거야?”국내기후자료 - 한국[김대중 前 대통령 서거] 과감한 구조개혁 'DJ노믹스'로 최단기간 환란극복 :: 네이버 뉴스“이라크 "韓-쿠르드 유전개발 MOU 승인 안해"(종합)”“해외 우리국민 추방사례 43%가 일본”차기전차 K2'흑표'의 세계 최고 전력 분석, 쿠키뉴스 엄기영, 2007-03-02두산인프라, 헬기잡는 장갑차 'K21'...내년부터 공급, 고뉴스 이대준, 2008-10-30과거 내용 찾기mk 뉴스 - 구매력 기준으로 보면 한국 1인당 소득 3만弗과거 내용 찾기"The N-11: More Than an Acronym"Archived조선일보 최우석, 2008-11-01Global 500 2008: Countries - South Korea“몇년째 '시한폭탄'... 가계부채, 올해는 터질까”가구당 부채 5000만원 처음 넘어서“‘빚’으로 내몰리는 사회.. 위기의 가계대출”“[경제365] 공공부문 부채 급증…800조 육박”“"소득 양극화 다소 완화...불평등은 여전"”“공정사회·공생발전 한참 멀었네”iSuppli,08年2QのDRAMシェア・ランキングを発表(08/8/11)South Korea dominates shipbuilding industry | Stock Market News & Stocks to Watch from StraightStocks한국 자동차 생산, 3년 연속 세계 5위자동차수출 '현대-삼성 웃고 기아-대우-쌍용은 울고' 과거 내용 찾기동반성장위 창립 1주년 맞아Archived"중기적합 3개업종 합의 무시한 채 선정"李대통령, 사업 무분별 확장 소상공인 생계 위협 질타삼성-LG, 서민업종인 빵·분식사업 잇따라 철수상생은 뒷전…SSM ‘몸집 불리기’ 혈안Archived“경부고속도에 '아시안하이웨이' 표지판”'철의 실크로드' 앞서 '말(言)의 실크로드'부터, 프레시안 정창현, 2008-10-01“'서울 지하철은 안전한가?'”“서울시 “올해 안에 모든 지하철역 스크린도어 설치””“부산지하철 1,2호선 승강장 안전펜스 설치 완료”“전교조, 정부 노조 통계서 처음 빠져”“[Weekly BIZ] 도요타 '제로 이사회'가 리콜 사태 불러들였다”“S Korea slams high tuition costs”““정치가 여론 양극화 부채질… 합리주의 절실””“〈"`촛불집회'는 민주주의의 질적 변화 상징"〉”““촛불집회가 민주주의 왜곡 초래””“국민 65%, "한국 노사관계 대립적"”“한국 국가경쟁력 27위‥노사관계 '꼴찌'”“제대로 형성되지 않은 대한민국 이념지형”“[신년기획-갈등의 시대] 갈등지수 OECD 4위…사회적 손실 GDP 27% 무려 300조”“2012 총선-대선의 키워드는 '국민과 소통'”“한국 삶의 질 27위, 2000년과 2008년 연속 하위권 머물러”“[해피 코리아] 행복점수 68점…해외 평가선 '낙제점'”“한국 어린이·청소년 행복지수 3년 연속 OECD ‘꼴찌’”“한국 이혼율 OECD중 8위”“[통계청] 한국 이혼율 OECD 4위”“오피니언 [이렇게 생각한다] `부부의 날` 에 돌아본 이혼율 1위 한국”“Suicide Rates by Country, Global Health Observatory Data Repository.”“1. 또 다른 차별”“오피니언 [편집자에게] '왕따'와 '패거리 정치' 심리는 닮은꼴”“[미래한국리포트] 무한경쟁에 빠진 대한민국”“대학생 98% "외모가 경쟁력이라는 말 동의"”“특급호텔 웨딩·200만원대 유모차… "남보다 더…" 호화病, 고질병 됐다”“[스트레스 공화국] ① 경쟁사회, 스트레스 쌓인다”““매일 30여명 자살 한국, 의사보다 무속인에…””“"자살 부르는 '우울증', 환자 중 85% 치료 안 받아"”“정신병원을 가다”“대한민국도 ‘묻지마 범죄’,안전지대 아니다”“유엔 "학생 '성적 지향'에 따른 차별 금지하라"”“유엔아동권리위원회 보고서 및 번역본 원문”“고졸 성공스토리 담은 '제빵왕 김탁구' 드라마 나온다”“‘빛 좋은 개살구’ 고졸 취업…실습 대신 착취”원본 문서“정신건강, 사회적 편견부터 고쳐드립니다”‘소통’과 ‘행복’에 목 마른 사회가 잠들어 있던 ‘심리학’ 깨웠다“[포토] 사유리-곽금주 교수의 유쾌한 심리상담”“"올해 한국인 평균 영화관람횟수 세계 1위"(종합)”“[게임연중기획] 게임은 문화다-여가활동 1순위 게임”“영화속 ‘영어 지상주의’ …“왠지 씁쓸한데””“2월 `신문 부수 인증기관` 지정..방송법 후속작업”“무료신문 성장동력 ‘차별성’과 ‘갈등해소’”대한민국 국회 법률지식정보시스템"Pew Research Center's Religion & Public Life Project: South Korea"“amp;vwcd=MT_ZTITLE&path=인구·가구%20>%20인구총조사%20>%20인구부문%20>%20 총조사인구(2005)%20>%20전수부문&oper_YN=Y&item=&keyword=종교별%20인구& amp;lang_mode=kor&list_id= 2005년 통계청 인구 총조사”원본 문서“한국인이 좋아하는 취미와 운동 (2004-2009)”“한국인이 좋아하는 취미와 운동 (2004-2014)”Archived“한국, `부분적 언론자유국' 강등〈프리덤하우스〉”“국경없는기자회 "한국, 인터넷감시 대상국"”“한국, 조선산업 1위 유지(S. Korea Stays Top Shipbuilding Nation) RZD-Partner Portal”원본 문서“한국, 4년 만에 ‘선박건조 1위’”“옛 마산시,인터넷속도 세계 1위”“"한국 초고속 인터넷망 세계1위"”“인터넷·휴대폰 요금, 외국보다 훨씬 비싸”“한국 관세행정 6년 연속 세계 '1위'”“한국 교통사고 사망자 수 OECD 회원국 중 2위”“결핵 후진국' 한국, 환자가 급증한 이유는”“수술은 신중해야… 자칫하면 생명 위협”대한민국분류대한민국의 지도대한민국 정부대표 다국어포털대한민국 전자정부대한민국 국회한국방송공사about korea and information korea브리태니커 백과사전(한국편)론리플래닛의 정보(한국편)CIA의 세계 정보(한국편)마리암 부디아 (Mariam Budia),『한국: 하늘이 내린 한 폭의 그림』, 서울: 트랜스라틴 19호 (2012년 3월)대한민국ehehehehehehehehehehehehehehWorldCat132441370n791268020000 0001 2308 81034078029-6026373548cb11863345f(데이터)00573706ge128495

            Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition