blocks|key|849990|text|感谢codaddict提出了-i选项。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|849991|以下命令解决了Snow+Leopard上的问题|849992|sed+-i+''+-e's/[+\t]*$//'+"$1"|code-block|syntax|javascript|849993|entityMap^0|E|2|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|R|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|S|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

Thanks to codaddict for suggesting the <code>-i</code> option.

The following command solves the problem on Snow Leopard

<pre><code>sed -i '' -e's/[ \t]*$//' "$1"
</code></pre>

blocks|key|1064214|text|您可以在Linux和Unix上使用sed的就地选项-i：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1064215|sed+-i+'s/[+\t]*$//'+"$1"|code-block|syntax|javascript|1064216|请注意，表达式将在OSX上删除尾随的t(您可以使用gsed来避免此问题)。它也可能在BSD上删除它们。|1064217|如果您没有gsed，下面是OSX上正确的(但难以阅读的)+sed语法：|1064218|sed+-i+''+-E+'s/[+'$'\t'']%2B$//'+"$1"|1064219|三个单引号的字符串最终连接成一个参数/表达式。bash中没有连接运算符，您只需将字符串一个接一个地放在一起，中间没有空格。|1064220|$'\t'在bash中解析为文字制表符字符(使用ANSI-C+quoting)，因此制表符被正确地连接到表达式中。|1064221|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.bash-hackers.org/syntax/quoting#ansi_c_like_strings^0|H|3|P|2|0|0|I|1|P|4|0|0|0|0|0|5|O|E|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|17|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|18|8|@$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1D|8|@]|D|@]|E|$]]|$1|O|3|P|5|H|7|1E|8|@]|D|@]|E|$I|J]]|$1|Q|3|R|5|6|7|1F|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1G|8|@$9|1H|A|1I|B|C]]|D|@$9|1J|A|1K|1|1L]]|E|$]]|$1|U|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]]]

You can use the in place option <code>-i</code> of <code>sed</code> for Linux and Unix:

<pre><code>sed -i 's/[ \t]*$//' "$1"
</code></pre>

Be aware the expression will delete trailing <code>t</code>'s on OSX (you can use <code>gsed</code> to avoid this problem). It may delete them on BSD too.

If you don't have gsed, here is the correct (but hard-to-read) sed syntax on OSX:

<pre><code>sed -i '' -E 's/[ '$'\t'']+$//' "$1"
</code></pre>

Three single-quoted strings ultimately become concatenated into a single argument/expression. There is no concatenation operator in bash, you just place strings one after the other with no space in between.

The <code>$'\t'</code> resolves as a literal tab-character in bash (using <a href="http://wiki.bash-hackers.org/syntax/quoting#ansi_c_like_strings" rel="noreferrer">ANSI-C quoting</a>), so the tab is correctly concatenated into the expression.

blocks|key|1064409|text|至少在Mountain+Lion上，Viktor的答案也会在行尾去掉字符't‘。以下是解决该问题的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1064410|sed+-i+''+-e's/[[:space:]]*$//'+"$1"|code-block|syntax|javascript|1064411|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|$]]

At least on Mountain Lion, Viktor's answer will also remove the character 't' when it is at the end of a line. The following fixes that issue:

<pre><code>sed -i '' -e's/[[:space:]]*$//' "$1"
</code></pre>

blocks|key|1064428|text|最好也引用$1：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1064429|sed+-i.bak+'s/[[:blank:]]*$//'+"$1"|code-block|syntax|javascript|1064430|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|$]]

It is best to also quote $1:

<pre><code>sed -i.bak 's/[[:blank:]]*$//' "$1"
</code></pre>

blocks|key|850102|text|var1="\t\t+Test+String+trimming+++"
echo+$var1
Var2=$(echo+"${var1}"+%7C+sed+'s/%5E[[:space:]]*//;s/[[:space:]]*$//')
echo+$Var2|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|850103|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>var1="\t\t Test String trimming "
echo $var1
Var2=$(echo "${var1}" | sed 's/^[[:space:]]*//;s/[[:space:]]*$//')
echo $Var2
</code></pre>

blocks|key|1064477|text|我的.bashrc中有一个可以在OSX和Linux下运行的脚本(仅限bash+!)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1064478|function+trim_trailing_space()+{
++if+[[+$#+-eq+0+]];+then
++++echo+"$FUNCNAME+will+trim+(in+place)+trailing+spaces+in+the+given+file+(remove+unwanted+spaces+at+end+of+lines)"
++++echo+"Usage+:"
++++echo+"$FUNCNAME+file"
++++return
++fi
++local+file=$1
++unamestr=$(uname)
++if+[[+$unamestr+==+'Darwin'+]];+then
++++#specific+case+for+Mac+OSX
++++sed+-E+-i+''++'s/[[:space:]]*$//'+$file
++else
++++sed+-i++'s/[[:space:]]*$//'+$file
++fi
}|code-block|syntax|javascript|1064479|我要补充的是：|1064480|SRC_FILES_EXTENSIONS="js%7Cts%7Ccpp%7Cc%7Ch%7Chpp%7Cphp%7Cpy%7Csh%7Ccs%7Csql%7Cjson%7Cini%7Cxml%7Cconf"

function+find_source_files()+{
++if+[[+$#+-eq+0+]];+then
++++echo+"$FUNCNAME+will+list+sources+files+(having+extensions+$SRC_FILES_EXTENSIONS)"
++++echo+"Usage+:"
++++echo+"$FUNCNAME+folder"
++++return
++fi
++local+folder=$1

++unamestr=$(uname)
++if+[[+$unamestr+==+'Darwin'+]];+then
++++#specific+case+for+Mac+OSX
++++find+-E+$folder+-iregex+'.*\.('$SRC_FILES_EXTENSIONS')'
++else
++++#Rhahhh,+lovely
++++local+extensions_escaped=$(echo+$SRC_FILES_EXTENSIONS+%7C+sed+s/\%7C/\\\\\%7C/g)
++++#echo+"extensions_escaped:$extensions_escaped"
++++find+$folder+-iregex+'.*\.$'$extensions_escaped'$$'
++fi
}

function+trim_trailing_space_all_source_files()+{
++for+f+in+$(find_source_files+.);+do+trim_trailing_space+$f;done
}|1064481|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I have a script in my .bashrc that works under OSX and Linux (bash only !)

<pre class="lang-bash prettyprint-override"><code>function trim_trailing_space() {
 if [[ $# -eq 0 ]]; then
 echo "$FUNCNAME will trim (in place) trailing spaces in the given file (remove unwanted spaces at end of lines)"
 echo "Usage :"
 echo "$FUNCNAME file"
 return
 fi
 local file=$1
 unamestr=$(uname)
 if [[ $unamestr == 'Darwin' ]]; then
 #specific case for Mac OSX
 sed -E -i '' 's/[[:space:]]*$//' $file
 else
 sed -i 's/[[:space:]]*$//' $file
 fi
}
</code></pre>

to which I add:

<pre class="lang-bash prettyprint-override"><code>SRC_FILES_EXTENSIONS="js|ts|cpp|c|h|hpp|php|py|sh|cs|sql|json|ini|xml|conf"

function find_source_files() {
 if [[ $# -eq 0 ]]; then
 echo "$FUNCNAME will list sources files (having extensions $SRC_FILES_EXTENSIONS)"
 echo "Usage :"
 echo "$FUNCNAME folder"
 return
 fi
 local folder=$1

 unamestr=$(uname)
 if [[ $unamestr == 'Darwin' ]]; then
 #specific case for Mac OSX
 find -E $folder -iregex '.*\.('$SRC_FILES_EXTENSIONS')'
 else
 #Rhahhh, lovely
 local extensions_escaped=$(echo $SRC_FILES_EXTENSIONS | sed s/\|/\\\\\|/g)
 #echo "extensions_escaped:$extensions_escaped"
 find $folder -iregex '.*\.$'$extensions_escaped'$$'
 fi
}

function trim_trailing_space_all_source_files() {
 for f in $(find_source_files .); do trim_trailing_space $f;done
}
</code></pre>

blocks|key|850305|text|对于那些追求效率(要处理的文件很多，或者文件很大)的人来说，使用%2B重复操作符而不是*可以使命令速度提高两倍以上。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|850306|使用GNU+sed：|850307|sed+-Ei+'s/[+\t]%2B$//'+"$1"
sed+-i+'s/[+\t]\%2B$//'+"$1"+++#+The+same+without+extended+regex|code-block|syntax|javascript|850308|我还快速测试了其他一些东西:使用[+\t]而不是[[:space:]]也大大加快了这个过程(GNU+sed+v4.4)：|850309|sed+-Ei+'s/[+\t]%2B$//'+"$1"

real++++0m0,335s
user++++0m0,133s
sys+0m0,193s

sed+-Ei+'s/[[:space:]]%2B$//'+"$1"

real++++0m0,838s
user++++0m0,630s
sys+0m0,207s

sed+-Ei+'s/[+\t]*$//'+"$1"

real++++0m0,882s
user++++0m0,657s
sys+0m0,227s

sed+-Ei+'s/[[:space:]]*$//'+"$1"

real++++0m1,711s
user++++0m1,423s
sys+0m0,283s|850310|entityMap^0|W|1|15|1|0|0|0|G|5|O|B|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|14|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|R|$]]

For those who look for efficiency (many files to process, or huge files), using the <code>+</code> repetition operator instead of <code>*</code> makes the command more than twice faster.

With GNU sed:

<pre><code>sed -Ei 's/[ \t]+$//' "$1"
sed -i 's/[ \t]\+$//' "$1" # The same without extended regex
</code></pre>

I also quickly benchmarked something else: using <code>[ \t]</code> instead of <code>[[:space:]]</code> also significantly speeds up the process (GNU sed v4.4):

<pre><code>sed -Ei 's/[ \t]+$//' "$1"

real 0m0,335s
user 0m0,133s
sys 0m0,193s

sed -Ei 's/[[:space:]]+$//' "$1"

real 0m0,838s
user 0m0,630s
sys 0m0,207s

sed -Ei 's/[ \t]*$//' "$1"

real 0m0,882s
user 0m0,657s
sys 0m0,227s

sed -Ei 's/[[:space:]]*$//' "$1"

real 0m1,711s
user 0m1,423s
sys 0m0,283s
</code></pre>

blocks|key|850110|text|只是为了好玩：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|850111|#!/bin/bash

FILE=$1

if+[[+-z+$FILE+]];+then
+++echo+"You+must+pass+a+filename+--+exiting"+>&2
+++exit+1
fi

if+[[+!+-f+$FILE+]];+then
+++echo+"There+is+not+file+'$FILE'+here+--+exiting"+>&2
+++exit+1
fi

BEFORE=`wc+-c+"$FILE"+%7C+cut+--delimiter='+'+--fields=1`

#+>>>>>>>>>>
sed+-i.bak+-e's/[+\t]*$//'+"$FILE"
#+<<<<<<<<<<

AFTER=`wc+-c+"$FILE"+%7C+cut+--delimiter='+'+--fields=1`

if+[[+$?+!=+0+]];+then
+++echo+"Some+error+occurred"+>&2
else
+++echo+"Filtered+'$FILE'+from+$BEFORE+characters+to+$AFTER+characters"
fi|code-block|syntax|javascript|850112|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|$]]

Just for fun:

<pre><code>#!/bin/bash

FILE=$1

if [[ -z $FILE ]]; then
 echo "You must pass a filename -- exiting" &gt;&amp;2
 exit 1
fi

if [[ ! -f $FILE ]]; then
 echo "There is not file '$FILE' here -- exiting" &gt;&amp;2
 exit 1
fi

BEFORE=`wc -c "$FILE" | cut --delimiter=' ' --fields=1`

# &gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;
sed -i.bak -e's/[ \t]*$//' "$FILE"
# &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;

AFTER=`wc -c "$FILE" | cut --delimiter=' ' --fields=1`

if [[ $? != 0 ]]; then
 echo "Some error occurred" &gt;&amp;2
else
 echo "Filtered '$FILE' from $BEFORE characters to $AFTER characters"
fi
</code></pre>

blocks|key|1064623|text|要仅从至少包含一个非空格字符的行中剥离空格(在我的示例中为空格和制表符)(这样就不会接触空缩进的行)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1064624|sed+-i+-r+'s/([%5E+\t]%2B)[+\t]%2B$/\1/'+"$file"|code-block|syntax|javascript|1064625|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|$]]

To only strip whitespaces (in my case spaces and tabs) from lines with at least one non-whitespace character (this way empty indented lines are not touched):

<pre class="lang-sh prettyprint-override"><code>sed -i -r 's/([^ \t]+)[ \t]+$/\1/' "$file"
</code></pre>

I have a simple shell script that removes trailing whitespace from a file. Is there any way to make this script more compact (without creating a temporary file)?

<pre><code>sed 's/[ \t]*$//' $1 &gt; $1__.tmp
cat $1__.tmp &gt; $1
rm $1__.tmp
</code></pre>

How to remove trailing whitespaces with sed?

Linux

Unix

我有一个简单的shell脚本，可以删除文件中的尾随空格。有没有办法使这个脚本更紧凑(不创建临时文件)？sed 's/[ \t]*$//' $1 > $1__.tmpcat $1__.tmp > $1rm $1__.tmp

问如何使用sed删除尾随空格？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用sed删除尾随空格？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用sed删除尾随空格？
EN