Insert line commands, e.g. I, TS,

Stef:
This is what happens when we try to be more efficient in one area and it comes back to bite.

The process for removal of unused ****** lines used to scan the whole file after each Enter to do this.   When users started loading in very large files (hundreds of thousands of lines), this scanning became a big overhead item.

So we altered it and started tracking where the inserted lines were and only checked those locations.  That corrected the overhead problem.

However, it works based on the assumption that you insert some lines, do something with those inserted lines and then hit Enter.

Your scenario inserted the lines, then wandered off to do an 'R' command somewhere else, and then hit Enter.  And the 'R' command shifted all the line numbers.

So the saved locations of the ****** lines no longer matched, and the unused ****** lines were not processed.

I'm afraid right now this might have to remain an annoyance.  I'll try and see if I can make a work-around, but because there are just SO many line and primary commands that can alter line numbers I doubt I can do it.   I do not want to fall back to the full file scan methodology.

George

OK, I've had a look at this.   As I thought, there's no simple work-around, I'm afraid this will remain a 'live with it' quirk.  Sorry.

The proper fix would need a change to every spot where lines can be added or deleted.  As you can figure, this is quite extensive. Considering the impact this would mean, it will have to wait for the next time some major work is done.

George