Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The problem can be reproduced on Linux with this sequence: 1. Run git gui from a terminal. 2. Edit the commit message and wait for at least 2 seconds. 3. Terminate the instance from the terminal, for example with Ctrl-C, to simulate crash. This leaves the file .git/GITGUI_BCK behind. 4. Start two instances of git gui &. At this point the first instance can be closed (it renames .git/GITGUI_BCK to .git/GITGUI_MSG), but the seconds brings an error message about the absent file and cannot be closed thereafter and must be killed from the command line. The renaming that happens by the first instance is the correct action and need not be repeated by the second instance. It is the correct action to ignore the failed renaming. On the other hand, the second instance could just edit the commit message again, wait 2 seconds to write GITGUI_BCK, and then can be closed without failing. At this point, since the user has edited the message, it is again correct to preserve the edited version in GITGUI_MSG. * os/catch-rename: git-gui: fix inability to quit after closing another instance
- Loading branch information