On 2019-06-10 3:39 PM, Donald Russell wrote: > Pipe ahelp xedit > > Use it to read starting at the current line, use subsequent stages to > select/do what you want.
As I said: >> If I know I'm not going to add or delete >> anything past the current line or change DISPLAY or SCOPE, I can use >> EXTRACT /NBSCOPE to compute a number of lines for TAKE: If I might change DISPLAY or SCOPE, though, or add, delete, or change the SELECT level of lines between the current line and the target line, all bets are off. Even if I duplicated all of XEDIT's target processing (relative and absolute numeric targets, line names, string expressions affected by ZONE, CASE, ARBCHAR, SPAN, VARBLANK, etc.), I wouldn't have the original contents of the file in the pipeline to process. My first thought was that I could use a line name to keep track: SET POINT at the target beforehand, and then after processing each line EXTRACT /LINE/POINT to see if I've reached it or it's disappeared. But that requires choosing a point name to reserve that can't be used by any subcommands issued to XEDIT--or any other instance of this stage--while the pipeline is running. ¬R
