Here's a general approach for problems like this, where you want to isolate a specific token and work on it, adapted for your problem:
#!/bin/sed -f
:loop # while the line has a matching token
/([^)]*[0-9]\+[^)])/ {
s//\n&\n/ # mark it -- \n is good as a marker because it is
# nowhere else in the line
h # hold the line!
s/.*\n\(.*\)\n.*/\1/ # isolate the token
s/[0-9]\+,\s*//g # work on the token. Here this removes all numbers
s/,\s*[0-9]\+//g # with or without commas in front or behind
s/\s*[0-9]\+\s*//g
s/\s*()// # and also empty parens if they exist after all that.
G # get the line back
# and replace the marked token with the result of the
# transformation
s/\(.*\)\n\(.*\)\n.*\n\(.*\)/\2\1\3/
b loop # then loop to get all such tokens.
}
To those who argue that this goes beyond the scope of what should reasonably be done with sed I say: True, but...well, true. But if all you see is nails, this is a way to make sed into a sledgehammer.
This can of course be written inline (although that does not help readability):
echo 'Foo 12 (bar, 12)' | sed ':loop;/([^)]*[0-9]\+[^)])/{;s//\n&\n/;h;s/.*\n\(.*\)\n.*/\1/;s/[0-9]\+,\s*//g;s/,\s*[0-9]\+//g;s/\s*[0-9]\+\s*//g;s/\s*()//;G;s/\(.*\)\n\(.*\)\n.*\n\(.*\)/\2\1\3/;b loop}'
but my advice is to put it into a file and run echo 'Foo 12 (bar, 12)' | sed -f foo.sed
. Or, with the shebang like above, chmod +x foo.sed
and echo 'Foo 12 (bar, 12)' | ./foo.sed
.
I have not benchmarked this, by the way. I imagine that it is not the most efficient way to process large amounts of data.
EDIT: In response to the comments: I'm not sure what OP wants in such cases, but for the sake of completion, the basic pattern could be adapted for the other behavior like this:
#!/bin/sed -f
:loop
/(\s*[0-9]\+\s*)\|(\s*[0-9]\+\s*,[^)]*)\|([^)]*,\s*[0-9]\+\s*)\|([^)]*,\s*[0-9]\+\s*,[^)]*)/ {
s//\n&\n/
h
s/.*\n\(.*\)\n.*/\1/
s/,\s*[0-9]\+\s*,/,/g
s/(\s*[0-9]\+\s*,\s*/(/
s/\s*,\s*[0-9]\+\s*)/)/
s/\s*(\s*[0-9]*\s*)//
G
s/\(.*\)\n\(.*\)\n.*\n\(.*\)/\2\1\3/
b loop
}
The regex at the top looks a lot scarier now. It should help to know that it consists of the four subpatterns
(\s*[0-9]\+\s*)
(\s*[0-9]\+\s*,[^)]*)
([^)]*,\s*[0-9]\+\s*)
([^)]*,\s*[0-9]\+\s*,[^)]*)
which are or-ed together with \|
. This should cover all cases and not match things like foo12
, 12bar
, and foo12bar
in parentheses (unless there's a standalone number in them as well).