-
-
Notifications
You must be signed in to change notification settings - Fork 688
Open
Description
Steps to reproduce
- Run
set confirm
- Create a few buffers with unsaved changes (doesn't matter if the buffers are backed by files or not).
- Run command
macaction terminate:
, or press Cmd-Q, or reboot machine.
Expected behaviour
The setting set confirm
should prompt for each unsaved buffer whether you are okay with discarding changes. However, macaction terminate:
completely ignores this setting, and just shows a dialog that doesn't mention any file names:
Quit without saving?
There are modified buffers, if you quit now all changes will be lost. Quit anyway?
It appears that macaction terminate:
skips a lot of normal Vim exit code as well - autocommands like VimLeavePre
do not run.
Version of MacVim
r181
MacVim installation method
GitHub release
Environment
macOS 15.4.1 Sequoia
Logs and stack traces
N/A
Vim and MacVim configuration where issue is reproducable
Doesn't appear to depend on config. I tested both with mvim --clean
and my usual config, https://github.com/telotortium/vimrc
How was MacVim launched?
- by launching MacVim.app in macOS (by using the Dock, Spotlight, or the
open
command) - by running mvim/gvim in the terminal
Issue has been tested with clean configuration
- by running
mvim --clean
(orgvim
, supplied by MacVim distribution). You can also use the File → "New Clean Window" menu item within MacVim. - by running
vim --clean
(in terminal, supplied by MacVim distribution) - by running
vim --clean
(in terminal, other suppliers, e.g. /usr/bin/vim)
Metadata
Metadata
Assignees
Labels
No labels