Hide

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.


If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Hide

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Remove color codes (special characters) with sed

Terminal - Remove color codes (special characters) with sed
sed -r "s/\x1B\[([0-9]{1,2}(;[0-9]{1,2})?)?[m|K]//g"
2009-09-23 12:06:33
User: Cowboy
Functions: sed
19
Remove color codes (special characters) with sed

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives
sed -r "s:\x1B\[[0-9;]*[mK]::g"'
sed -r "s/\x1B\[([0-9]{1,3}((;[0-9]{1,3})*)?)?[m|K]//g
2009-11-03 00:34:06
User: vaejovis
Functions: sed
4

Removes ANSI color and end of line codes to the [{attr1};...;{attrn}m format.

sed "s,\x1B\[[0-9;]*[a-zA-Z],,g"
2013-03-18 14:49:30
User: Zhoul
Functions: sed
1

Remove ( color / special / escape / ANSI ) codes, from text, with sed

Credit to the original folks who I've copied this command from.

The diff here is:

Theirs: [m|K]

Theirs is supposed to remove \E[NUMBERS;NUMBERS[m OR K]

This statement is incorrect in 2 ways.

1. The letters m and K are two of more than 20+ possible letters that can end these sequences.

2. Inside []'s , OR is already assumed, so they are also looking for sequences ending with | which is not correct.

This : [a-zA-Z]

This resolves the "OR" issue noted above, and takes care of all sequences, as they all end with a lower or upper cased letter.

This ensures 100% of any escape code 'mess' is removed.

sed -r 's/'$(echo -e "\033")'\[[0-9]{1,2}(;([0-9]{1,2})?)?[mK]//g'
2012-01-04 20:57:09
User: frntn
Functions: echo sed
Tags: bash sed
0

Remove ANSI colors from stream or file

sed -r "s/\x1B\[([0-9]{1,2}(;[0-9]{1,2})?)?[m|K]//g"
2012-06-12 11:20:46
User: rcbarnes
Functions: sed
0

Handles the color codes intended for 256-color terminals (such as xterm-(256)color and urxvt-unicode-256color), in addition to the standard 16-color ANSI forms. Overkill for strict ANSI output, see other options for something simpler.

Know a better way?

If you can do better, submit your command here.

What others think

See also http://www.pixelbeat.org/scripts/ansi2html.sh for other possible codes to strip

Comment by pixelbeat 257 weeks and 2 days ago

Just what I needed for cleaning the capture of the 'script' command. Thanks!

Comment by funollet 251 weeks and 3 days ago

Does this work when you have 2 colors on a line?

Comment by matthewbauer 250 weeks and 6 days ago

badass. nice seddage :)

i wonder if there is a simpler way to do it with simple redirection of stdout.. hmm not sure yet. anyway awesome, i'm using this for now xD

Comment by kevinquinnyo 133 weeks and 5 days ago

FWIW, the `-r` does not work with `sed` on Mac OS-X.

Comment by jaytaylor 61 weeks ago

Here's the OS X equivalent:

sed -E "s/"$'\E'"\[([0-9]{1,3}((;[0-9]{1,3})*)?)?[m|K]//g

Note:

-E is the OS X equivalent of the -r option.

$'\E' splices a literal Escape character into the regex, because OS X sed doesn't recognize the \xnn escapes.

Also:

One of the ()? constructs is redundant, because it is covered by the enclosed ()*.

The '|' is probably misplaced, as the enclosing construct is the set operator, not an alternative, so '[mK]' is sufficient.

The terminal 'K' relates to the 'Erase in Line' command, and not a color or style, and thus may not be needed.

You only need *3* digits for *non-standard* sequences relating to aixterm, according to http://en.wikipedia.org/wiki/ANSI_escape_sequences#CSI_codes; if you only care about standard behavior, 2 digits will do.

With the above in mind, we get the following:

Linux:

sed -r "s/\x1B\[([0-9]{1,2}(;[0-9]{1,2})*)?m//g

OS X:

sed -E "s/"$'\E'"\[([0-9]{1,2}(;[0-9]{1,2})*)?m//g
Comment by mklement0 54 weeks and 4 days ago

Is there any way to undo the effect of sed command?

Comment by Wajiha 18 weeks and 4 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts