It appears every attempt to open a new MacVim window also encounters this. Until keychain adds identities to the agent, each attempt to spawn a new shell effectively blocks. New invocations of the shell prompt for the SSH key passphrase and block new shell instances until entered, or until an error causes keychain to exit.
running from start script in Terminal.Įval $(keychain -quiet -eval -agents ssh id_rsa) I'll review settings but it's not clear to me why a customization would cause failures running from finder vs. Afterward, MacVim launched correctly (rendered windows) from Finder. When the issue occurs, it's frustrating and I move on, but at some point I switch back to the MacVim task and open a new window, and it just works as if there was never an issue.Īs an experiment I backed up and removed my existing. I've seen this behavior in several macOS releases now over the years. It's running and responding appropriately, but not rendering a window when launched from Finder. The Window menu does not list any open app windows. Cmd-O opens a dialog to select a file to open, but opening a file does not render an editor window for the file. Everything is as it should be.īut when launching from Finder (either Cmd-space and typing MacVim.app, or double clicking the app bundle from the Applications folder, the app runs it creates an icon in the dock, it presents a menu, but it doesn't render a window for the editor. When I launch MacVim using the mvim script from Terminal, it launches the app and renders a GUI window.
This is macvim: ,169 (auto_updates) installed as a cask from Homebrew.
0 kommentar(er)
