|
Post by Stefan on Apr 23, 2022 6:25:53 GMT -5
Hi George,
The description of changes for v22109 beta includes this statement:
Correct handling of RESET [COMMAND]. Processing was not correctly distinguishing User issued RESET commands from internally issued RESET commands.
Also ensure the WORD, HIDE and SOURCE operands are properly exempted from ALL processing.
This doesn't seem to be working correctly. Both RESET (with no operands) and RESET ALL will 'undo' the HIDE setting. And RESET ALL also appears to revert the WORD definition to the A-Z a-z 0-9 default value.
I also figure that if a setting is not within the scope of RESET ALL, it probably shouldn't be in scope for a RESET (without operands) either.
In the case of HIDE, I tested using...
(1) Issue HIDE X ON
(2) Exclude some lines XX...XX block ==> Excluded lines are truely invisible (3) Issue RESET or RESET ALL
==> Effectively does RESET X and HIDE (4) Exclude some lines XX..XX block ==> Excluded lines are shown with the usual "-------- <0000n> ---" marker I expected if RESET and RESET ALL do not include HIDE, the lines excluded in step (4) should still be invisible.
|
|
|
Post by George on Apr 23, 2022 9:54:32 GMT -5
Stefan: Ick! Residual code buried in there. Now removed.
No operand and ALL are still different however:
RESET (No Operands) ALL minus = Retrieve, Label, Tag, Command, Word, Hide, Source, Track (And User if set in Options)
RESET ALL ALL - Retrieve, Word, Hide, Source
I'll update the RESET Help, it's probably not correct.
George
|
|