George,
I have silent data loss issues with SAVE.
(1) I loaded file BACKVIEW.MACRO
(2) Made some cosmetic changes to displayed values - (text in quoted strings, etc)
(3) Issued BACKVIEW ? ALL to see what the current backup messages looked like
(4) Entered SAVE
(5) Issued BACKVIEW ? ALL to see what the revised backup message looked like, but...
I see only message Missing / Invalid Macro header line
Perfectly accurate! There's no data in the BACKVIEW.MACRO file any more.
I had missed the message after step (4) that said 0 records written to file - it should have been 280 records written to file
All this despite the fact that I am looking at 280 lines of BackView code in the still open edit tab.
/UPDATE
I can can't reproduce the exact issue above and BACKView is too complicated anyway.
But can offer a version of the error with this greatly simpler test scenario...
(1) Load the attached GPL-3.TXT file into the editor.
(2) Issue primary command LINE .16 GNOTE3
(3) Issue SAVE
Most probably SPFlite will return message 1 records written to file
Clearly incorrect when you're still looking at 600+ lines.
The saved line is usually the one specified in the LINE primary command (line 16 in the above example)
Subsequently other weird stuff can happen...
- A subsequent macro opens an SPF_DEBUG window even though the macro contains no SPF_DEBUG statements.
- SAVE continues not to work unless you REPLACE GPL-3.TXT to properly "restore/save" the current file.
After that, SAVE is fine, so the problem is caused by insertion of the NOTE lines.
Hope this helps