Getting my password wrong locks my vim for 30s

[n0v1c3]

Getting my password wrong locks my vim for 30s

[mikeboiko]

I like the idea of logging in asynchronously!

[n0v1c3]

I did reduce the timeout. Believe me it used to be a 8 minute crash when I was first setting it up 😓. What it needs now is a simple try catch and the red lines can go away and it should be closer to a 15 second Vim Crash.

echo Connecting to ...
3 attempts with 5 second time out
echo Connected/Failed: ERROR <er #>

I will probably reduce the 3 attempts to 1 and let the user try again on their own. This also help reduce the chance of locking yourself out.

[n0v1c3]

The reduction in the number of tries will be the major reduction in time Vim locked for. I should also be able to run this as a parallel process and simply use the out and statusline to show what is going on.

[n0v1c3]

I have moved this along with some other login issues to "Highest" priority and should be patched soon.

[mikeboiko]

Sweet, thanks!

…

On Tue, Feb 5, 2019, 8:35 AM Travis Gall ***@***.*** wrote: I have moved this along with some other login issues to "Highest" priority and should be patched soon. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#20 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXG2eG1aGR-ahTBO1eMTd3zcd-h2L21gks5vKaS9gaJpZM4aiW2_> .

[n0v1c3]

Other than a coffee I should not miss this evening and a job in my way looking at the list I should be able to fix most of it by tonight or tomorrow night.

[mikeboiko]

Right on!

…

On Tue, Feb 5, 2019, 8:40 AM Travis Gall ***@***.*** wrote: Other than a coffee I should not miss this evening and a job in my way looking at the list I should be able to fix most of it by tonight or tomorrow night. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#20 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXG2eIadekqqJaAGvU42bPL8SrkIGyEGks5vKaYBgaJpZM4aiW2_> .

[n0v1c3]

This issue should be fixed on the master branch