|
|
Post by George on May 5, 2021 13:21:16 GMT -5
Robert: Hmmm, you must be using the new 2.5. In 2.4 ALL works. For now in 2.5 use .ZF .ZL.
George
|
|
|
|
Post by George on May 5, 2021 13:57:45 GMT -5
Robert: Not a problem, actually, if you can continue to use 2.5, all the better. Just be aware it is a very early version, and the whole primary command parsing has been taken apart and put together differently. I've done cursory checking of each primary command (wow, was that painful). But stuff like this will continue to fall out.
But we can now do what Stefan reported. i.e. do a FIND/CHANGE, then an Exclude of a line range, and then still do an RFIND based on the original FIND/CHANGE.
It was a much bigger change than I anticipated, because I kept running into the kind of code where you say "What was I thinking?". The code might work, but needed a bit of TLC to re-arrange things.
George
|
|
|
|
Post by George on May 5, 2021 14:22:25 GMT -5
Robert: As I worked through it, it became obvious that there were just too many layers of F/C parameters. Mix in what were basically PUSH/POP routines trying to save/restore status and it was, frankly, an ungodly mess. Also throw in a weird custom routine that tried to parse out a filename along with command line range operands, or, line command CC blocks (For commands like CREATE/REPLACE), and it was a big mess. Somehow it all worked, but really an embarrassing pile of code.
Much cleaner now, the whole Find/Change criteria block is now kept in an Object, which makes things a whole lot simpler. Only problem was that this took a ridiculous number of changes to switch from individual global variables to Object properties.
George
|
|
