Here's another one of those »how much« questions. Objective 103.7 mentions »sed« (and used to in the previous version) under the heading of »Search text files using regular expressions«. The objective heading does not appear to cover anything other than searching, in which case
$ sed -n /foo/p file1 file2 file3 does pretty much what $ grep foo file1 file2 file3 gives you already (modulo differences in RE syntax and expressive power). If that is so, then what *other* uses of sed did the authors of the objective have in mind to warrant its inclusion? The objective text does say »manipulate files and text data using regular expressions« even though the title only mentions searching. Does that mean »sed s/.../.../«? »sed /.../c...?«? (I'm currently working on the RE part of our introductory docs. So far we have covered sed fairly extensively in the »shell programming« manual (the third in our old sequence), which according to our present planning is in LPI-102 territory. In the previous issue of our docs this wasn't as much of an issue as we didn't market the first two manuals as sufficient to pass LPI-101, which we intend to do now. I'd much rather not load the introductory manual with the sed chapter. I'd also rather avoid splitting the sed content in two. What to do?) Anselm -- Anselm Lingnau ... Linup Front GmbH ... Linux-, Open-Source- & Netz-Schulungen [email protected], +49(0)6151-9067-103, Fax -299, www.linupfront.de Linup Front GmbH, Postfach 100121, 64201 Darmstadt, Germany Sitz: Weiterstadt (AG Darmstadt, HRB7705), Geschäftsführer: Oliver Michel _______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
