-
-
Notifications
You must be signed in to change notification settings - Fork 35
First require locks up neovim for ~10 seconds #82
Comments
@devth Thank you for the reporting! Does this problem occur in any project? |
I tried it in my yetibot project. It seems to repro on any file I try requiring after initial Trying on a fresh project doesn't seem to freeze:
In neovim: nvim src/iced_repro/core.clj
:IcedConnect
# nvim freezes for about 1 second
<Leader>eb
# no freeze So it doesn't appear to happen on a fresh project. I'll keep playing with it. Maybe has to do with how much source code is in the project? |
Noticed a large error after connecting and trying to
After that when I try to |
@devth I couldn't reproduce the problem with following steps...
I uses nvim 0.3.2.
It seems to me you use nvim 0.3.2(nightly), so could you update nvim 0.3.2(released) or later and test again? |
Upgraded to
|
@devth Thanks! |
Strange. I will also keep testing on my side and see if I can narrow down what's going on! |
The fact that "Required" is output means I made a minimal configuration for vim-iced for breaking down this problem. |
Sorry for the delay. I was able to repro the same issue in the paired down |
@devth cider-nrepl plugin injects all cider-nrepl middlewares containing
|
Amazing! Nice job. I will try this out soon. I always thought |
@devth Other plugins may require I'll fix to work with |
I'm having a similar issue with my shadow-cljs project. It seems that shadow-cljs includes the At the moment there's no way to turn this feature off. |
@knubie Wow! That's awesome!! |
Closed by branching to #170 |
After
:IcedConnect
the first:IcedRequire
locks up neovim for about 10 seconds. During this time I can't move the cursor or do anything inside neovim. After that subsequent:IcedRequire
s run nearly instantly.Ref #77
The text was updated successfully, but these errors were encountered: