You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not entirely sure this is related to vim-ultest rather than nvim itself, but when I first installed the plugin, the popup window with the failed test information took exactly 4 seconds to display (the one that pops up on hover on the first line of the failed test).
I checked with :options and found out that I had updatetime set to 4000 (which, I guess, is the default value). Reducing it to 100 actually makes the popup window appear instantly.
However, this will cause a lot more writes (40 times more) to the swap file, if it's used, therefor raising a potential issue on SSD devices. I would add this information to the readme, either telling users to disable swap files or to know the tradeoffs of a low updatetime.
Thanks for this plugin and keep up the great work!
The text was updated successfully, but these errors were encountered:
It shouldn't depend on the updatetime value, I can confirm I set mine to 4000 and it still opens immediately. I imagine there is something else causing the delay. Could you provide some more info on your version, system and logs please?
Edit: On a second look I see I was wrong, it does depend on updatetime. I will add this to the docs, thanks!
Describe the bug
I'm not entirely sure this is related to
vim-ultest
rather than nvim itself, but when I first installed the plugin, the popup window with the failed test information took exactly 4 seconds to display (the one that pops up on hover on the first line of the failed test).I checked with
:options
and found out that I hadupdatetime
set to4000
(which, I guess, is the default value). Reducing it to100
actually makes the popup window appear instantly.However, this will cause a lot more writes (40 times more) to the swap file, if it's used, therefor raising a potential issue on SSD devices. I would add this information to the readme, either telling users to disable swap files or to know the tradeoffs of a low
updatetime
.Thanks for this plugin and keep up the great work!
The text was updated successfully, but these errors were encountered: