How to add a line in files recursively bash?
I use the command to add one line at the beginning of the php files in the current directory and its subdirrectories recursively.
find . -name "*.php" -exec sed -i -e "/<?php/a\
Sometext" *.php ;
But it adds Sometext
many times (instead of one) only in php files in the current directory (instead of all). What I did wrong?
bash
add a comment |
I use the command to add one line at the beginning of the php files in the current directory and its subdirrectories recursively.
find . -name "*.php" -exec sed -i -e "/<?php/a\
Sometext" *.php ;
But it adds Sometext
many times (instead of one) only in php files in the current directory (instead of all). What I did wrong?
bash
add a comment |
I use the command to add one line at the beginning of the php files in the current directory and its subdirrectories recursively.
find . -name "*.php" -exec sed -i -e "/<?php/a\
Sometext" *.php ;
But it adds Sometext
many times (instead of one) only in php files in the current directory (instead of all). What I did wrong?
bash
I use the command to add one line at the beginning of the php files in the current directory and its subdirrectories recursively.
find . -name "*.php" -exec sed -i -e "/<?php/a\
Sometext" *.php ;
But it adds Sometext
many times (instead of one) only in php files in the current directory (instead of all). What I did wrong?
bash
bash
asked Nov 13 '18 at 15:28
FoxFox
3961419
3961419
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You don't pass the files found by find
to the sed
command, but the files found by the shell glob *.php
. Before find
is executed, the *.php
is expanded and your command becomes
find . -name '*.php' -exec sed ... 1stMatch.php 2ndMatch.php ... ;
Afterwards, find
will for each found file execute the command
sed ... 1stMatch.php 2ndMatch.php ...
You probably wanted to write
find . -name '*.php' -exec sed -i -e '/<?php/a\
Sometext' ;
For each file, find
executes sed
and replaces by one file name.
In this case, you could even write +
instead of ;
such that sed
is executed only once on all files at once, instead of once for every file – this will speed up your command drastically.
Thanks a lot. This helped.
– Fox
Nov 13 '18 at 15:35
Sure I will. Just it asks me to wait 6 mins to be able to accept.
– Fox
Nov 13 '18 at 15:42
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53284298%2fhow-to-add-a-line-in-files-recursively-bash%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You don't pass the files found by find
to the sed
command, but the files found by the shell glob *.php
. Before find
is executed, the *.php
is expanded and your command becomes
find . -name '*.php' -exec sed ... 1stMatch.php 2ndMatch.php ... ;
Afterwards, find
will for each found file execute the command
sed ... 1stMatch.php 2ndMatch.php ...
You probably wanted to write
find . -name '*.php' -exec sed -i -e '/<?php/a\
Sometext' ;
For each file, find
executes sed
and replaces by one file name.
In this case, you could even write +
instead of ;
such that sed
is executed only once on all files at once, instead of once for every file – this will speed up your command drastically.
Thanks a lot. This helped.
– Fox
Nov 13 '18 at 15:35
Sure I will. Just it asks me to wait 6 mins to be able to accept.
– Fox
Nov 13 '18 at 15:42
add a comment |
You don't pass the files found by find
to the sed
command, but the files found by the shell glob *.php
. Before find
is executed, the *.php
is expanded and your command becomes
find . -name '*.php' -exec sed ... 1stMatch.php 2ndMatch.php ... ;
Afterwards, find
will for each found file execute the command
sed ... 1stMatch.php 2ndMatch.php ...
You probably wanted to write
find . -name '*.php' -exec sed -i -e '/<?php/a\
Sometext' ;
For each file, find
executes sed
and replaces by one file name.
In this case, you could even write +
instead of ;
such that sed
is executed only once on all files at once, instead of once for every file – this will speed up your command drastically.
Thanks a lot. This helped.
– Fox
Nov 13 '18 at 15:35
Sure I will. Just it asks me to wait 6 mins to be able to accept.
– Fox
Nov 13 '18 at 15:42
add a comment |
You don't pass the files found by find
to the sed
command, but the files found by the shell glob *.php
. Before find
is executed, the *.php
is expanded and your command becomes
find . -name '*.php' -exec sed ... 1stMatch.php 2ndMatch.php ... ;
Afterwards, find
will for each found file execute the command
sed ... 1stMatch.php 2ndMatch.php ...
You probably wanted to write
find . -name '*.php' -exec sed -i -e '/<?php/a\
Sometext' ;
For each file, find
executes sed
and replaces by one file name.
In this case, you could even write +
instead of ;
such that sed
is executed only once on all files at once, instead of once for every file – this will speed up your command drastically.
You don't pass the files found by find
to the sed
command, but the files found by the shell glob *.php
. Before find
is executed, the *.php
is expanded and your command becomes
find . -name '*.php' -exec sed ... 1stMatch.php 2ndMatch.php ... ;
Afterwards, find
will for each found file execute the command
sed ... 1stMatch.php 2ndMatch.php ...
You probably wanted to write
find . -name '*.php' -exec sed -i -e '/<?php/a\
Sometext' ;
For each file, find
executes sed
and replaces by one file name.
In this case, you could even write +
instead of ;
such that sed
is executed only once on all files at once, instead of once for every file – this will speed up your command drastically.
edited Nov 13 '18 at 15:38
answered Nov 13 '18 at 15:34
SocowiSocowi
6,2202724
6,2202724
Thanks a lot. This helped.
– Fox
Nov 13 '18 at 15:35
Sure I will. Just it asks me to wait 6 mins to be able to accept.
– Fox
Nov 13 '18 at 15:42
add a comment |
Thanks a lot. This helped.
– Fox
Nov 13 '18 at 15:35
Sure I will. Just it asks me to wait 6 mins to be able to accept.
– Fox
Nov 13 '18 at 15:42
Thanks a lot. This helped.
– Fox
Nov 13 '18 at 15:35
Thanks a lot. This helped.
– Fox
Nov 13 '18 at 15:35
Sure I will. Just it asks me to wait 6 mins to be able to accept.
– Fox
Nov 13 '18 at 15:42
Sure I will. Just it asks me to wait 6 mins to be able to accept.
– Fox
Nov 13 '18 at 15:42
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53284298%2fhow-to-add-a-line-in-files-recursively-bash%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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