macvim-dev / macvim-dev/macvim

After waking up computer from Sleep, Macvim will try to close

Open
#1,459 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Vim Script
Stars
7.9k
Forks
691
PR merge metrics
No merged PRs in 30d

Description

Steps to reproduce

Open a file with MacVim
Lock computer and wait 5-10min
Unlock computer
Macvim will be either closed or a popup will appear to confirm if you want to close MacVim with unsaved buffers.

Expected behaviour

I expect MacVim to no close itself.

This only happen with MacVim hence I think it is an issue with MacVim...
I've tried to look at debug logs but I don't see anything useful.

Maybe you guys have an idea how to trace back the event that was sent to MacVim ?

Version of Vim and architecture

VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Sep 12 2023 09:31:27) macOS version - x86_64 Included patches: 1-1897 Compiled by GitHub Actions

MacVim r178 (Vim 9.0.1897)

Environment

MacOs Sonoma 14.1.1 (23B81)
Iterm

How MacVim was installed

Downloaded last release via Github

Logs and stack traces

No response

Vim configuration where issue is reproducable

No response

Issue has been tested with given configuration
  • by running MacVim.app from GUI macOS interface
  • by running vim/gvim/etc installed by MacVim
  • by running other versions of vim (e.g. /usr/bin/vim)
Issue has been tested with no configuration
  • by running mvim --clean (or gvim, supplied by MacVim distribution)
  • by running vim --clean (in terminal, supplied by MacVim distribution)
  • by running vim --clean (in terminal, other suppliers, e.g. /usr/bin/vim)
Other conditions
  • The both Homebrew packages "vim" and "macvim" are installed

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with MacVim.app from the macOS GUI, first using mvim --clean, after locking and waking the computer. Inspect the available debug logs and trace which event causes MacVim to close or show the unsaved-buffers prompt. Done means MacVim remains open after wake without prompting to close.

Written by the indexing model from the issue text.

Assessment

Tech stack
macos, vim
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.