Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"After last window closes" setting ignored #1338

Closed
GT-GH opened this issue Nov 4, 2022 · 5 comments · Fixed by #1339
Closed

"After last window closes" setting ignored #1338

GT-GH opened this issue Nov 4, 2022 · 5 comments · Fixed by #1339
Milestone

Comments

@GT-GH
Copy link

GT-GH commented Nov 4, 2022

The current version of MacVim (9.0.472) seems to be ignoring the setting for "After last window closes" when set to "Quit MacVim". After I quit all editor windows, MacVim remains open. I'm on a Mac M1 Max running Monterey 12.5.1, if it helps.

@ychin
Copy link
Member

ychin commented Nov 4, 2022

What are you other settings? In particular, what's your setting on "Open untitled window"? #1257 made a change so that you cannot have both "Open untitled window" = "never", and "After last window closes" = "Quit MacVim". If you think about these two settings they kind of don't make any sense together. If you try to set them in the settings pane, setting one should automatically change the other one to something else now.

@GT-GH
Copy link
Author

GT-GH commented Nov 4, 2022

You're right, that was the issue. Thank you!

Still, I don't think that change makes sense and I hope you consider rolling it back. These settings DO make sense together. The "Open untitled window" setting should only be checked on launch (and a new window opened if needed). The "After last window closes" setting should only be checked after at least one window had been actively closed by the user (i.e., not on launch).

I practically never need a new/blank document to open on launch, it only adds an unnecessary step to my process. On the other hand, I don't want a zombie process lingering after I'm done editing my last file.

@ychin
Copy link
Member

ychin commented Nov 4, 2022

Hmm, I see. I didn't think this was actually a real use case, but I can consider addressing it. It likely won't be a direct rollback since the previous implementation was buggy (just opening and closing "About MacVim" would randomly quit the app. In fact I can see this behavior in iTerm as well) and macOS-behavior-specific but I can try to make it only start to activate the "After last window closes" after the first window has showed up.

@ychin ychin added this to the Release 175 milestone Nov 4, 2022
@GT-GH
Copy link
Author

GT-GH commented Nov 4, 2022

I appreciate it very much, and thank you also for providing this excellent editor on the Mac platform!

@ychin ychin added UI Issues related to UI elements, tabs, scrollbars, window resizing, etc. and removed UI Issues related to UI elements, tabs, scrollbars, window resizing, etc. labels Nov 4, 2022
ychin added a commit to ychin/macvim that referenced this issue Nov 5, 2022
…last window"

This reverts commit f6ba7dd.

This change was reverted as part of macvim-dev#1338 as we want to implement a
different solution.
ychin added a commit to ychin/macvim that referenced this issue Nov 5, 2022
Previously we disabled this combo in f6ba7dd because when
implemented naively, it causes an issue where just opening an About
MacVim or Settings window could immediately cause MacVim to exit
(because macOS determined that there were no non-auxillary window open).
This was awkward and potentially made it hard to change the setting
back, and was depending on OS behavior. However, it seems like there are
legit use case for this combo of settings. Change it so that we allow
setting both of them, but add checks so that
`applicationShouldTerminateAfterLastWindowClosed:` will only return
`YES` if we have opened at least one Vim window before. This gives the
user a chance to open a window first, so using Settings etc wouldn't
immediately terminate the app.

Fix macvim-dev#1338
@ychin
Copy link
Member

ychin commented Nov 5, 2022

Ok #1339 will address this. This should be part of the next release (r175) which I hope would be out soon-ish but some other issues are preventing it so working on those.

ychin added a commit to ychin/macvim that referenced this issue Nov 5, 2022
Previously we disabled this combo in f6ba7dd because when
implemented naively, it causes an issue where just opening an About
MacVim or Settings window could immediately cause MacVim to exit
(because macOS determined that there were no non-auxillary window open).
This was awkward and potentially made it hard to change the setting
back, and exact behavior depended on OS behavior.

However, it seems like there are legit use case for this combo of
settings. Change it so that we allow setting both of them again, but add
checks so that `applicationShouldTerminateAfterLastWindowClosed:` will
only return `YES` if we have opened at least one Vim window before. This
gives the user a chance to open a window first, so using Settings etc
wouldn't immediately terminate the app.

Fix macvim-dev#1338
ychin added a commit that referenced this issue Feb 7, 2023
Updated to Vim 9.0.1276

Features
====================

Dictionary lookup
--------------------

You can now use Force Touch or Cmd-Ctrl-D to look up definitions of word
under the cursor (or selected text in visual mode). This will also
preview URLs, and support data types such as phone numbers and
addresses. #1312 #1313

This feature can also be invoked programmatically from VimScript (see
`:h macvim-lookup`). #1315

Tool bar / Touch Bar / menu icons
--------------------

You can now use SF Symbols for Tool bar and Touch Bar icons, including
using different symbol styles such as "palette" or "multicolor". Menu
items can now also use the `icon=` syntax to specify icons as well. See
`:help macvim-toolbar-icon` for details. #1329

The default tool bar also has updated icons to look similar to SF
Symbols used by newer macOS versions. #1214 by @sfsam

Window management actions
--------------------

There are new `macaction`'s for managing the MacVim window. The new
`zoomLeft`/`zoomRight` actions allow you to pin the window to the
left/right of the screen, and there are also new actions for interacting
with Stage Manager (requires macOS 13+). See `:h macvim-actions` for
details. #1330

Pre-release updates / Sparkle 2
--------------------

MacVim now supports pre-release software builds. It's sometimes hard for
us to release frequent updates due to the desire to pick a stable
upstream Vim version, needing to test the release on multiple OS
versions, making sure there aren't half-complete or buggy features, and
other reasons.

This new feature now allows us to push pre-release beta builds out in a
more frequent fashion, which could be useful if there are particular
features or fixes that you would like to try out before the next
official release. Pre-release builds will be released depending on bug
fixes and features instead of a fixed cadence. Do note that these
pre-release builds may not be as well-validated and may have half-baked
features.

If you are using the built-in auto-updater to update MacVim, you can
turn this on by going to Advanced settings pane, and enable "Enable
pre-release software updates".

This feature is only available for macOS 10.13 or above.

The auto-updater has also been updated from Sparkle 1.27.1 to 2.3.0 for
10.13+ builds. Legacy (10.9-10.12) builds are still using Sparkle 1.

See #1332.

New Vim features
--------------------

New `smoothscroll` option allows you to scroll through a long wrapped
line (using Ctrl-E or mouse wheel) without immediately jumping to the
next line. (v9.0.0640)

`splitscroll` option has been renamed `splitkeep`, with more flexibility
than before. (v9.0.0647)

Sound playback on macOS is now supported. You can use `has('sound')` to
check. See `help sound` for details. (v9.0.0694)

Terminals now support `:confirm` for `:q`, etc, which also means
MacVim's Cmd-W will work properly for terminal windows. (v9.0.0710)

Virtual text had numerous bugs fixed.

General
====================

Legacy build for 10.9 - 10.12
--------------------

Per a previous announcement (#1271), the default MacVim binary will now
require macOS 10.13 or above. Users of macOS 10.9 - 10.12 can use a
separate "legacy" build which will still be supported. The legacy binary
will still have the latest versions of Vim and be supported, but may not
have all the latest features (e.g. pre-release builds).

If you are using the auto-updater (Sparkle) to update MacVim, it should
"just work" and find the best version for you. If you are downloading
MacVim from the website, there is also a link to download the legacy
version marked for 10.9+ as well. If you download the normal binary
marked for 10.13+ from the website, it won't work on these older macOS
versions.

See #1331.

Fixes
====================

CoreText Renderer clipping and rendering bugs
--------------------

Unicode characters with multiple composing characters (e.g. "x⃗") will
now render correctly. #1172

Texts (e.g. Tibetan, Zalgo texts) that are taller than the line height
will no longer be clipped inappropriately. You can use a new setting
`MMRendererClipToRow` to re-enable clipping if the tall texts are
distracting. #995 / #1356

Tab crash
--------------------

Fixed a crash when opening new tabs that seems to only occur in macOS 13
Ventura. #1333

Other bugs
--------------------

- Fixed non-native full screen not working well with the notch on newer
  MacBook's when set to not show menu bar. You can also use
  `MMNonNativeFullScreenSafeAreaBehavior` to force MacVim to use the
  notch area as well if you don't mind some content being obscured. Note
  that the previous release also claimed it fixed this, but because the
  binary was built against an old macOS SDK (Big Sur), the fix did not
  work in the binary release. #1261
- Allow "Open untitled window: never" and "After last window closes:
  Quit MacVim" to be set together again. Added safeguards to make sure
  doing so won't immediately close the app. #1338
- Edit.Cut / Copy menu items will now be properly disabled when there
  isn't selected text. #1308
- Fixed potential `:emenu` crash when the menu is associated with an
  action in a non-valid mode. #1305
- Fixed bug where just bringing up the right-click (or the
  MacVim→Services) menu would somehow copy the selected texts to the
  system clipboard. #1300
- Fixed a Japanese input method bug where using left/right arrow to move
  to a different section of the input text would previously result in
  the candidate list not showing up at the correct position. #1312
- Fix non-CoreText renderer not handling text styles like strikethrough
  correctly (note: this renderer has been deprecated for a while and you
  should not use it). #1296
- This release uses an older sh/bash syntax file because the latest one
  in Vim has a bug. #1358

Misc
====================

New settings:

- "No drop shadows" (Appearance). #1301
- "Treat Ctrl-click as right-click" (Input) (#1326). This was previously
  configurable via command-line, but now also possible in the settings
  pane under the new "Input" category.

"About MacVim" now reports the version number in a clearer way with
clearly specified release number vs Vim version.

Known Issues
====================

Printing
--------------------

Printing using File→Print or `:hardcopy` is currently not working under
macOS 13 Ventura due to its removal of PostScript support in the Preview
app. This will be fixed in a later release. See the issue for
workarounds. #1347

Scripting
====================

- Scripting languages versions:
    - Perl is now built against 5.30, up from 5.18.
    - Ruby is now built against 3.2, up from 3.1.

Compatibility
====================

Requires macOS 10.9 or above. (10.9 - 10.12 requires downloading a
separate legacy build)

Script interfaces have compatibility with these versions:

- Lua 5.4
- Perl 5.30
- Python2 2.7
- Python3 3.10
- Ruby 3.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants