Attempt to fix the slow startup some people are having by using the vim/neovim job apis #3
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.
Attempt the solution proposed by @chemzqm in dag#34 (comment)
If someone could test it using vim on windows and let me know if it works that'd be great.
Vim's documentation for
job_start
seems to suggest that we might need to use aString
for{command}
on windows and aList
on unix:I'm not sure if this should be merged as the cause of the slowness might just be misconfiguration of fish (such as using
set fish_user_paths $fish_user_paths /new/path
in their config.fish, which will cause fish_user_paths to grow each time fish is started).