4

I am aware of another question that is quite similar, but for some reason I'm still having problems.

I have a GC log that I'm trying to trim out the Tenured section enclosed in [].

63.544: [GC 63.544: [DefNew: 575K->63K(576K), 0.0017902 secs]63.546: [Tenured: 1416K->1065K(1536K), 0.0492621 secs] 1922K->1065K(2112K), 0.0513331 secs]

I apply s/\[Tenured:.*\]//

And quite expectantly, the result is trimmed greedily through the remainder of the line:

63.544: [GC 63.544: [DefNew: 575K->63K(576K), 0.0017902 secs]63.546:

So let's try and be non-greedy not match a closing right bracket with s/\[Tenured:[^\]]*\]// but alas no match is made and sed skips over the line, producing the same original output:

63.544: [GC 63.544: [DefNew: 575K->63K(576K), 0.0017902 secs]63.546: [Tenured: 1416K->1065K(1536K), 0.0492621 secs] 1922K->1065K(2112K), 0.0513331 secs]

How do I non-greedily match and replace that section? Thanks,

Community
  • 1
  • 1
Jé Queue
  • 10,359
  • 13
  • 53
  • 61

4 Answers4

5

Almost: s/\[Tenured:[^]]*\]//

The manual says:

To include a literal ']' in the list, make it the first character (following a possible '^').

i.e. No backslash is required in this context.

  • Raz
3
sed -e 's/\[Tenured:[^]]*\]//'

Apparently you shouldn't escape the close square bracket. Wacky!

From man re_format:

A bracket expression is a list of characters enclosed in '[]' ... To include a literal ']' in the list, make it the first character (following a possible `^').

Laurence Gonsalves
  • 137,896
  • 35
  • 246
  • 299
0

Try .*? for the non-greedy variant of .*. (Not sure if it's supported in sed's regex engine or not, but it's worth a try.)

Edit: This previous SO question may be relevant - Non greedy regex matching in sed?

Community
  • 1
  • 1
Amber
  • 507,862
  • 82
  • 626
  • 550
0

This worked:

echo "63.544: [GC 63.544: [DefNew: 575K->63K(576K), 0.0017902 secs]63.546: [Tenured: 1416K->1065K(1536K), 0.0492621 secs] 1922K->1065K(2112K), 0.0513331 secs]" | sed -e s/\\[Tenured:[^\]]*\\]//
  • I think that works because the shell was doing the escaping prior to getting to sed. The same would not be true unfortunately for a sed script file. – Jé Queue Nov 06 '09 at 05:44