macvim-dev / macvim-dev/macvim

Use macOS cooperative app activation to activate app to foreground

Ouverte
#1,456 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

14.0 Sonoma
Langage dominant
Vim Script
Étoiles
7.9k
Forks
691
Métriques de merge des PR
Aucune PR mergée en 30 j

Description

macOS 14 Sonoma deprecated the NSApplication API activateIgnoringOtherApps, and provides a new activate API along with a cooperative yieldActivation command that can be called by the host app. We should switch to using this API.

One issue is that calling activate requires the foreground app to cooperate and willingly yield. There are a few usages of activateIgnoringOtherApps right now:

  1. Using the "New Window" menu item on the Dock icon. I think this actually works automatically and the activate call may be superfluous.
  2. Opening a new Vim from the mvim script so the new Vim window would be in foreground. This wouldn't work as the terminal has foreground. Calling :gui from non-GUI mode works similarly. (Note that currently directly invoking MacVim.app/Contents/MacOS/MacVim does not activate the app because of how the logic in addVimController but it's ok as it's not a normal path)
  3. Invoking :call foreground() in Vim. This also wouldn't just work as Vim does not have the right to gain activation when it's in background under this API model.
  4. When opening a file by dragging it to the dock, etc. This should work as MacVim should gain focus when that happens.
  5. Running the new XCTest test cases. This also wouldn't just work if running the tests from terminal (e.g. in CI we just run make -C src macvim-tests) as MacVim will fail to gain foreground this way. Running from Xcode will be fine though as Xcode will yield.

To fix 2/3/5, we probably need to run a simple Swift script that calls NSApplication.shared.yieldActivation(toApplicationWithBundleIdentifier: "org.vim.MacVim") to manually force the terminal to yield to MacVim. For 2 and 5, we can call them as part of the mvim script and Makefile, respectively.

For 3, it's a little tricky. If the foreground request is invoked as a remote call using the --remote family of commands, it would work, but MacVim will lose the ability to randomly bring itself to the foreground at will (e.g. running :sleep 2 | call foreground() would not work). This is probably ok as the foreground() API doesn't work on Win32 too and in general it's best to let the foreground app has agency over when focus unless the user manually clicked away.

Currently, in macOS 14, the activateIgnoringOtherApps API is only deprecated but it still works so there's no reason to do anything. Just keep this in mind for now. If macOS 15 formally breaks it, we will implement the fix along with the manual yielding from terminal so that calling mvim from terminal, running tests etc would still work. We don't really want to do anything until this API breaks because even fixing it "properly" we will still lose case (3) where call foreground() will stop working if not called using --remote.

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Commencez par les sites d’appel de activateIgnoringOtherApps indiqués, notamment addVimController, le script mvim, l’exécution de XCTest pilotée par Makefile et foreground(). Confirmez le comportement d’activation de macOS et déterminez quels chemins nécessitent un yielding coopératif. Le travail est considéré comme terminé lorsque le chemin d’activation obsolète est remplacé tout en préservant le comportement du dock et de l’ouverture des fichiers, et que la limitation de foreground() est documentée.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
macos, swift
Domaine
desktop, operating-systems
Type d'issue
Fonctionnalité
Difficulté
4/5
Temps estimé
3-5 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
38/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.