On Wed, Jan 18, 2006 at 07:15:44PM -0800, Todd Walton wrote:
> So. Back to sed. I was hoping for a conceptual overview of the
> different parts of a sed command line. The man page says:
>
> "sed [OPTION]... {script-only-if-no-other-script} [input-file]..."
>
> So, we have the command, 'sed'. Then options to sed. Then... what?
> And the file we're performing the operation on. Presumably the file
> is optional, and stdin is okay. It occurred to me a while ago that my
> "Linux in a Nutshell" book has a whole section on sed (and awk) but I
> can't seem to find it.
>
> I'm guessing that script-only-blah part is where I put the edits to
> perform. These edits come in the form of options? (dash-something) I
> know for sure that sed does the s/// substitute, but most edits don't
> look like that, right? I think maybe s/// is all I need for my
> purposes, though. Do I just stick it in here?
>
> What am I doing??? Gawd don't make me have to use 'info'.
>
Well, since you're going into this with eyes as open as they're allowing
you, I will say this: When I had to hack/maintain some sed/awk legacy
stuff, I found the O'Reilly book quite helpful. I will confess, I got
rid of it as soon as I left that gig, but assuming (again) that you have
no recourse, it's a good book.
http://www.oreilly.com/catalog/sed2/
Can you get Tcl/Tk? It has everything the growing boy needs for regexes
etc, albeit without perl's orientation toward that kind of processing.
--
Lan Barnes [EMAIL PROTECTED]
Linux Guy, SCM Specialist 858-354-0616
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
