Startup of vim-fish is insanely slow #34
Comments
|
Any update on this? I had to uninstall vim-fish because of it |
|
Ditto, still no updates from me. I just uninstalled it @pierrebeaucamp |
|
Ubuntu 14.04, Fish 2.4.0, vim-fish 825853f (master) |
|
Can you checkout |
|
Also, @pierrebeaucamp are you also using Homebrew and Neovim? Is it easy for you try with normal Vim, not in home brew? |
|
I'm using Neovim. I checked out master, but it still takes multiple seconds to load. Longest file to load is |
|
This seems to have fixed it for myself in both vim and neovim (sorry @pierrebeaucamp!), thanks for the update @ElijahLynn |
|
@kyleholzinger So to confirm, you are using |
|
@ElijahLynn Yes sir! I'm on |
|
I'm running into the slowness issue as well. I use:
Both installed via homebrew. I ran: Click "Details" below to see the log. Note the following line: |
|
Mind blowingly slow for me, wow. Any direction on how to improve the load time? |
|
@babakness can you run vim with And post here the contents of In my case I have solved the problem after I noticed incorrectly configured fish, specifically the usage of |
|
@gmile |
|
similar issue with |
|
@babakness can you run this: And post the contents of |
|
I'm just starting out with fish and I had this problem too. My Removing it caused vim-fish to launch smoothly. |
|
Talk about specific lol. That seems unrelated to this plugin, I wanna say... |
|
I'm closing this, as I've had my issue solved. Thank you @ElijahLynn ! |
|
Reopening because others reported slowness as well, but didn't report it being solved. I would guess the slowness comes either from Those of you experiencing slowness: is fish itself similarly slow to start? |
|
Just a 5 cents: it is very likely that people use When in need to add something to path, instead of doing this (which I did and which was wrong): set fish_user_paths $fish_user_paths /new/pathOne must do this: set fish_user_paths /new/path
set fish_user_paths /new/path /another/new/path /and/another/one
I recognized this specifically by running benchmarks built into
|
|
Hmm, |
|
@dag good point, I mistyped that! Updated the comment to have |
|
Ah you mean, this might be causing |
|
Yes, I think it is |
|
I found |
|
I had uninstalled this plugin due to the same issue. However, I had also been noticing that the startup time for fish shell itself was getting longer and longer. I found that I was incorrectly setting |
|
@dag Thanks, |
|
hmm, I found it is still slow when I put anyenv init code in config.fish: eval (anyenv init - fish | source)When I put |
|
There is job for vim & neovim could be used to avoid the block running system command. |
|
I'm definitely still experiencing slowness. After profiling, I was able to narrow down the problem to ftplugin but beyond that, I'm not sure. I've also tried the suggestion of |
|
Takes 3 seconds longer to start Neovim when opening a file of filetype In my case it seems to be because my Fish is slow at startup (because of something in my configuration, apparently), and Fish is for some reason called by Workaround (with reduced functionality): I commented out every Solution (for me): Clean up |
|
I attempted @chemzqm's suggestion if you'd like to try it out: If all of the cases of this slowness are traced to misconfiguration of fish, I probably won't merge it. |
|
Is there any chance running the job in the background results in undesired behavior? |
|
If something uses Vim's docs have some things that use Plugins may also use The worry is that this change might be added complication to solve a problem that's better solved outside of vim through fish configuration fixes. |
|
It seems the reason we're evaluating I actually hadn't fixed my problem with Thank you for your time, @blankname. |
|
my performance issues ended up being a misconfigured simple fix for me was to do the following:
echo $fish_user_paths > ~/fish_user_paths.bak
set updated_paths (echo $fish_user_paths | tr " " "\n" | sort -r | uniq)
echo $updated_paths | tr " " "\n" | nl
set --universal fish_user_paths $updated_paths |
I've been loving using fish, but I've found that the startup time of this plugin is super slow, upwards of 5 seconds sometimes. I've pasted below a bit of the output of my
vim --startuptime vim.log test.fishcommand. Is there any way to improve the performance? I'm not sure if it's just me, but I'd definitely like to use this plugin without the startuptime lagThe text was updated successfully, but these errors were encountered: