Re: OT: sed -n vs. sed
On Sat, May 15, 2004 at 05:35:24PM -0500, Kirk Strauser wrote:
> At 2004-05-15T21:53:42Z, William Ballard <40414.nospam@comcast.net> writes:
>
> > What semantically huge iceberg of a use case am I missing that makes "sed
> > -n" useful?
>
> Ever notice that sed can be scripted, and that it has commands that tell it
> to print the current pattern space? You can write a sed script that only
> prints a few specific items this way.
Apparently only p and P print *anything* if -n is in effect; which means
no other command has any visible side effects; you can only store the
result in hold space, until you print it with p.
Is that the basic approach? And isn't perl better for program-y things
anyway?
Reply to: