adamyg/grief

Win32 v3.2.2, Alt-X does nothing if the file being edited has been changed but not saved

Closed this issue · 2 comments

First, thank you for both Grief and the Windows version of Midnight Commander!

Using the Win32 version 3.2.2 of Grief, if the file has been changed, but not saved with Alt-W, nothing happens if Alt-X is entered. Furthermore, F10 followed by exit doesn't work either (but abort does).

Is this the behavior you intended? I would have thought a message such as "File changed but not saved; reply W (save then exit), X (exit), Enter (continue Grief session)." would be appropriate.

Corrected for next release, Behavior should be as described below.

Alt-W: when the current buffer is dirty
Write successful.

Alt-W: when the current buffer is not dirty
Buffer has not been modified -- not written.

Alt-X: when one or more buffers are dirty.
x buffer has not been saved. Exit [ynw]?

F10, exit: when one or more buffers are dirty.
x buffer has not been saved. Exit [ynw]?

F10, exit: when the current buffer is not dirty
no action, exits

Note: Current behavior branch "topic/build-23"; next release

3.2.2-build23