G52/G92 offsets should be deactivated on M2/M30 according to RS274NGC standard.
With the current code persistence will by default automatically activate G52/G92 offset on restart and leave G92/G52 active after M2/M30.
The standard states that 'Persistence' means that the values will be stored on M2/M30, G52/G92 is deactivated and if necessary the offset can be restored using G92.3
As Point 1 clearly states, M2/M30 should reset G92/G52 (like 92.2).
'Persistence' as handled by the ini entry [RS274NGC] 'DISABLE_G92_PERSISTENCE' is with regard to the current G52/G92 offset values being stored in the 'var' file.
G52/G92 offsets should be deactivated on M2/M30 according to RS274NGC standard.
With the current code persistence will by default automatically activate G52/G92 offset on restart and leave G92/G52 active after M2/M30. The standard states that 'Persistence' means that the values will be stored on M2/M30, G52/G92 is deactivated and if necessary the offset can be restored using G92.3
As Point 1 clearly states, M2/M30 should reset G92/G52 (like 92.2).
'Persistence' as handled by the ini entry [RS274NGC] 'DISABLE_G92_PERSISTENCE' is with regard to the current G52/G92 offset values being stored in the 'var' file.
With this there no longer any need to warn about unexpected offsets on startup like this: https://linuxcnc.org/docs/html/gcode/coordinates.html#sec:g52