|
Post by Stefan on Oct 27, 2022 5:08:46 GMT -5
If I wish to retain changes I've made to a file, the 'normal' modus operandi is to I issue a SAVE command (ignoring the AUTOSAVE setting for a moment). I find it confusing that different 'special' tabs, like SET or CLIP operate differently. CLIP needs a save, SET, EFT, etc do not.
With 'SET' and 'EFT' session, attempts to SAVE the changes results in an unecessary error message. The reason for not needing to SAVE these session is purely a technical internal one. The user doesn't care about the difference.
I suggest we change the SAVE command to check if it is being issued for a 'SET' session. If so, it just does nothing.
|
|
|
Post by George on Oct 27, 2022 9:38:08 GMT -5
Stefan: Simply ignoring a user entered command, with no indication of any activity, nor any kind of message whatsoever is simply NOT a good idea.
George
|
|
|
Post by Stefan on Oct 27, 2022 12:30:56 GMT -5
Then perhaps replace the FAIL message, which leaves the offending command in the command line, with an informational (RC=0) reminder like "SAVE is unnecessary, END will commit changes or use CANCEL"
There is also the inconsistency. Why do/must SET and EFT sessions behave differently to any other EDIT tab?
Unlike other EDIT sessions, in SET and EFT sessions you cannot save interim changes without exiting the editor.
That's not a big deal for SET, but it might be for EFT which could well be a longer list with more complex statements and require some trial & error to determine the format that gives the desired result.
I believe(!) the out-of-the-box default for AUTOSAVE is OFF NOPROMPT. So by default, a simple END throws changes away without warning. For users who run with the default AUTOSAVE settings (OFF NOPROMPT), the fact that END 'sometimes' saves the changes must seem weird.
By they way, I found this when I accidentally entered END SAVE
Did you know that END someword is accepted, but the parser fails END someword anotherword
|
|
|
Post by George on Oct 27, 2022 13:18:14 GMT -5
Changing the message is trivial, I can certainly do that. Done.
AUTOSAVE default is 'OFF, PROMPT', which I think is appropriate.
Next Beta will allow BACKUP of CLIP, SET and EFT sessions - does that help?
For some unknown reason, the CMD table entry for END specified a max # of operands as 1 (even though it HAS no operands). Corrected it to 0
|
|
|
Post by George on Oct 27, 2022 14:54:16 GMT -5
I think the table error for END was just a simple Oops!
|
|