There are two ways to do it:
1) Use the select filter and a subfilter (but I haven't documented the subfilters yet).
2) Use two select filters. (This is the easiest and just as fast.)
I don't know what you're up against but doesn't the interface to the "selection" action have an "extract" option?
I hope subfilters are very powerful. With CUT.EXE, "-f2,4,6,8,10" will output precisely those five fields. Would I have to use *six* TPIPE selection filters to get rid of the ones Idon't want? That alone would be a couple hundred characters
I'm just playing with TPIPE. With seven text utils (grep, sed, wc, sort, tr, cut, egrep) I can do just about anything I want. I'd like to see TPIPE replace all of those and be super-fast but I doubt it will and I don't process enough data to get back the time I'd spent composing TPIPE commands. I suppose anyone who will use TPIPE regularly will have quite a collection of aliases
Are you going to be the go-between when the TextPipe engine doesn't do what it's supposed to? Will those folks be as timely as you when it comes to bug fixes? What ever happened to TPIPE /sort? I'll bet the recently discovered bug in TPIPE /grep (counting matches) isn't yours.