Repository navigation
fix: let a fresh install start without errors - #14
Merged
Merged
Conversation
harrisoncramer
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A fresh install of the config failed on its first start, on the Mac as well as on Linux. One file loaded a git helper while lazy.nvim was still reading plugin specs, before the plugins that helper needs were on disk. Loading it later exposed a loop between diffview and the helper, so diffview now loads it only when a keymap needs it.
The fzf build broke on every fresh install too. It called a function that fzf only defines once it has loaded, and lazy.nvim hid the failure. The build now runs fzf's install script directly and fails loudly if the script does.