blocks|key|624921|text|OS混合使用了BSD和GNU工具，所以最好总是查看文档(尽管我知道less甚至不符合OS手册页)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|624922|https://web.archive.org/web/20170808213955/https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/sed.1.html|624923|sed将-i之后的参数作为备份的扩展。为无备份提供空字符串(-i+'')。|624924|执行以下操作：|624925|find+.+-type+f+-name+'*.txt'+-exec+sed+-i+''+s/this/that/g+{}+%2B|624926|-type+f只是一个很好的实践；如果您给它一个或更多的目录，sed将会报错。|624927|与xargs相比，-exec更可取；您不需要费心使用-print0或其他任何东西。|624928|末尾的{}+%2B意味着find会将所有结果作为参数附加到被调用命令的一个实例中，而不是为每个结果重新运行它。(一个例外是当违反操作系统允许的命令行参数的最大数量时；在这种情况下，find将运行多个实例。)|624929|如果您收到类似"invalid+byte+sequence“的错误，通过在命令开头添加LC_ALL=C来强制使用标准语言环境可能会有所帮助，如下所示：|624930|LC_ALL=C+find+.+-type+f+-name+'*.txt'+-exec+sed+-i+''+s/this/that/g+{}+%2B|624931|entityMap|0|LINK|mutability|MUTABLE|url^0|X|4|0|0|3X|0|0|4|2|U|5|0|0|0|1R|0|0|7|0|1|5|9|5|Q|7|0|3|4|A|4|2G|4|0|17|8|0|0|20|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|17|8|@]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|H|3|I|5|6|7|1B|8|@$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1G|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|1K|8|@$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1N|8|@$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|R|3|S|5|6|7|1U|8|@$9|1V|A|1W|B|C]|$9|1X|A|1Y|B|C]|$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|T|3|U|5|6|7|21|8|@$9|22|A|23|B|C]]|D|@]|E|$]]|$1|V|3|W|5|6|7|24|8|@$9|25|A|26|B|C]]|D|@]|E|$]]|$1|X|3|-4|5|6|7|27|8|@]|D|@]|E|$]]]|Y|$Z|$5|10|11|12|E|$13|G]]]]

OS X uses a mix of BSD and GNU tools, so best always check the documentation (although I had it that <code>less</code> didn't even conform to the OS X manpage):
<a href="https://web.archive.org/web/20170808213955/https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/sed.1.html" rel="nofollow noreferrer">https://web.archive.org/web/20170808213955/https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man1/sed.1.html</a>
sed takes the argument after <code>-i</code> as the extension for backups. Provide an empty string (<code>-i ''</code>) for no backups.
The following should do:
<code>find . -type f -name '*.txt' -exec sed -i '' s/this/that/g {} +</code>
The <code>-type f</code> is just good practice; sed will complain if you give it a directory or so.
<code>-exec</code> is preferred over <code>xargs</code>; you needn't bother with <code>-print0</code> or anything.
The <code>{} +</code> at the end means that <code>find</code> will append all results as arguments to one instance of the called command, instead of re-running it for each result. (One exception is when the maximal number of command-line arguments allowed by the OS is breached; in that case <code>find</code> will run more than one instance.)
If you get an error like &quot;invalid byte sequence,&quot; it might help to force the standard locale by adding <code>LC_ALL=C</code> at the start of the command, like so:
<code>LC_ALL=C find . -type f -name '*.txt' -exec sed -i '' s/this/that/g {} +</code>

blocks|key|625131|text|对于mac，一种更类似的方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|625132|find+.+-name+'*.txt'+-print0+%7C+xargs+-0+sed+-i+""+"s/form/forms/g"|code-block|syntax|javascript|625133|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For the mac, a more similar approach would be this:

<pre><code>find . -name '*.txt' -print0 | xargs -0 sed -i "" "s/form/forms/g"
</code></pre>

blocks|key|410100|text|作为替代解决方案，我在Mac+OSX+10.7.5上使用此解决方案|type|unstyled|depth|inlineStyleRanges|entityRanges|data|410101|grep+-ilr+'old-word'+*+%7C+xargs+-I@+sed+-i+''+'s/old-word/new-word/g'+@|code-block|syntax|javascript|410102|归功于：Todd+Cesere's+answer|offset|length|410103|entityMap|0|LINK|mutability|MUTABLE|url|http://www.cyberciti.biz/faq/unix-linux-replace-string-words-in-many-files/^0|0|0|4|K|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

As an alternative solution, I'm using this one on Mac OSX 10.7.5

<pre><code>grep -ilr 'old-word' * | xargs -I@ sed -i '' 's/old-word/new-word/g' @
</code></pre>

Credit goes to: <a href="http://www.cyberciti.biz/faq/unix-linux-replace-string-words-in-many-files/" rel="noreferrer">Todd Cesere's answer</a>

blocks|key|410036|text|以上这些在OSX上都不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|410037|执行以下操作：|410038|perl+-pi+-w+-e+'s/SEARCH_FOR/REPLACE_WITH/g;'+*.txt|code-block|syntax|javascript|410039|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

None of the above work on OSX.

Do the following:

<pre><code>perl -pi -w -e 's/SEARCH_FOR/REPLACE_WITH/g;' *.txt
</code></pre>

blocks|key|410206|text|一个可以在Linux和Mac上运行的版本(通过在sed中添加-e开关)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|410207|export+LC_CTYPE=C+LANG=C
find+.+-name+'*.txt'+-print0+%7C+xargs+-0+sed+-i+-e+'s/this/that/g'|code-block|syntax|javascript|410208|entityMap^0|O|3|U|2|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|L|$]]

A version that works on both Linux and Mac OS X (by adding the <code>-e</code> switch to <code>sed</code>):

<pre><code>export LC_CTYPE=C LANG=C
find . -name '*.txt' -print0 | xargs -0 sed -i -e 's/this/that/g'
</code></pre>

blocks|key|410153|text|每当我输入这个命令时，我似乎总是用软管把它管起来，或者忘记了一个标志。我根据TaylanUB的回答在github上创建了一个Gist，从当前目录执行全局查找替换。这是特定于Mac+OSX的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|410154|https://gist.github.com/nateflink/9056302|offset|length|410155|这很好，因为现在我只需打开一个终端，然后复制进去：|410156|curl+-s+https://gist.github.com/nateflink/9056302/raw/findreplaceosx.sh+%7C+bash+-s+"find-a-url.com“”替换-a-url.com“|410157|你可能会得到一些奇怪的字节序列错误，所以下面是完整的代码：|410158|#!/bin/bash
#By+Nate+Flink

#Invoke+on+the+terminal+like+this
#curl+-s+https://gist.github.com/nateflink/9056302/raw/findreplaceosx.sh+%7C+bash+-s+"find-a-url.com"+"replace-a-url.com"

if+[+-z+"$1"+]+%7C%7C+[+-z+"$2"+];+then
++echo+"Usage:+./$0+[find+string]+[replace+string]"
++exit+1
fi

FIND=$1
REPLACE=$2

#needed+for+byte+sequence+error+in+ascii+to+utf+conversion+on+OSX
export+LC_CTYPE=C;
export+LANG=C;

#sed+-i+""+is+needed+by+the+osx+version+of+sed+(instead+of+sed+-i)
find+.+-type+f+-exec+sed+-i+""+"s%7C${FIND}%7C${REPLACE}%7Cg"+{}+%2B
exit+0|code-block|syntax|javascript|410159|entityMap|0|LINK|mutability|MUTABLE|url|1|https://gist.github.com/nateflink/9056302/raw/findreplaceosx.sh^0|0|0|15|0|0|0|8|1R|1|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@$D|11|E|12|1|13]]|A|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@$D|16|E|17|1|18]]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1A|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|C]]|X|$5|T|U|V|A|$W|Y]]]]

Whenever I type this command I always seem to hose it up, or forget a flag. I created a Gist on github based off of TaylanUB's answer that does a global find replace from the current directory. This is Mac OSX specific.

<a href="https://gist.github.com/nateflink/9056302" rel="nofollow">https://gist.github.com/nateflink/9056302</a>

It's nice because now I just pop open a terminal then copy in:

curl -s <a href="https://gist.github.com/nateflink/9056302/raw/findreplaceosx.sh" rel="nofollow">https://gist.github.com/nateflink/9056302/raw/findreplaceosx.sh</a> | bash -s "find-a-url.com" "replace-a-url.com"

You can get some weird byte sequence errors, so here is the full code:

<pre><code>#!/bin/bash
#By Nate Flink

#Invoke on the terminal like this
#curl -s https://gist.github.com/nateflink/9056302/raw/findreplaceosx.sh | bash -s "find-a-url.com" "replace-a-url.com"

if [ -z "$1" ] || [ -z "$2" ]; then
 echo "Usage: ./$0 [find string] [replace string]"
 exit 1
fi

FIND=$1
REPLACE=$2

#needed for byte sequence error in ascii to utf conversion on OSX
export LC_CTYPE=C;
export LANG=C;

#sed -i "" is needed by the osx version of sed (instead of sed -i)
find . -type f -exec sed -i "" "s|${FIND}|${REPLACE}|g" {} +
exit 0
</code></pre>

blocks|key|625447|text|如果您使用的是zsh终端，则可以使用通配符魔法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|625448|sed+-i+""+"s/search/high-replace/g"+*.txt|offset|length|style|CODE|625449|entityMap^0|0|0|15|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

If you are using a zsh terminal you're able to use wildcard magic:

<code>sed -i "" "s/search/high-replace/g" *.txt</code>

blocks|key|410423|text|我使用了这种格式-但是……我发现我必须运行它三次或更多次，才能让它真正改变我发现非常奇怪的每个实例。运行一次会更改每个文件中的一些内容，但不是全部。完全相同的字符串运行两到四次将捕获所有实例。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|410424|find+.+-type+f+-name+'*.txt'+-exec+sed+-i+''+s/thistext/newtext/+{}+%2B|code-block|syntax|javascript|410425|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I used this format - but...I found I had to run it three or more times to get it to actually change every instance which I found extremely strange. Running it once would change some in each file but not all. Running exactly the same string two-four times would catch all instances.

<pre><code>find . -type f -name '*.txt' -exec sed -i '' s/thistext/newtext/ {} +
</code></pre>

blocks|key|625468|text|find+.+-type+f+%7C+xargs+sed+-i+''+'s/string1/string2/g'|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|625469|有关更多信息，请参阅here。|unstyled|offset|length|625470|entityMap|0|LINK|mutability|MUTABLE|url|https://coderwall.com/p/n-sxiq/replace-a-string-recursively-in-a-directory-on-mac-os-x^0|0|A|4|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|R|8|@]|9|@$G|S|H|T|1|U]]|A|$]]|$1|I|3|-4|5|F|7|V|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

<pre><code>find . -type f | xargs sed -i '' 's/string1/string2/g'
</code></pre>

Refer <a href="https://coderwall.com/p/n-sxiq/replace-a-string-recursively-in-a-directory-on-mac-os-x" rel="nofollow noreferrer">here</a> for more info.

blocks|key|625389|text|https://bitbucket.org/masonicboom/serp是一个go实用程序(即跨平台)，在OSX上测试，它对给定目录中文件中的文本执行递归搜索和替换，并确认每次替换。它是新的，所以可能有buggy。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|625390|用法如下：|625391|$+ls+test
a++d++d2+z
$+cat+test/z
hi
$+./serp+--root+test+--search+hi+--replace+bye+--pattern+"*"+++++++++++++++++++++++++
test/z:+replace+hi+with+bye?+(y/[n])+y
$+cat+test/z
bye|code-block|syntax|javascript|625392|entityMap|0|LINK|mutability|MUTABLE|url|https://bitbucket.org/masonicboom/serp^0|0|12|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

<a href="https://bitbucket.org/masonicboom/serp" rel="nofollow">https://bitbucket.org/masonicboom/serp</a> is a go utility (i.e. cross-platform), tested on OSX, that does recursive search-and-replace for text in files within a given directory, and confirms each replacement. It's new, so might be buggy.

Usage looks like:

<pre><code>$ ls test
a d d2 z
$ cat test/z
hi
$ ./serp --root test --search hi --replace bye --pattern "*" 
test/z: replace hi with bye? (y/[n]) y
$ cat test/z
bye
</code></pre>

In the linux shell, the following command will recursively search and replace all instances of 'this' with 'that' (I don't have a Linux shell in front of me, but it should do).

<pre><code>find . -name "*.txt" -print | xargs sed -i 's/this/that/g'
</code></pre>

What will a similar command on OSX look like?

Recursive search and replace in text files on Mac and Linux

Linux

在linux shell中，以下命令将递归地搜索“this”的所有实例，并将其替换为“that”(我面前没有Linux shell，但它应该有)。find . -name "*.txt" -print | xargs sed -i 's/this/that/g'在OSX上类似的命令会是什么样子？

问在Mac和Linux上递归搜索和替换文本文件
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Mac和Linux上递归搜索和替换文本文件EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Mac和Linux上递归搜索和替换文本文件
EN