Open larsks opened 4 years ago
This just hit me too, would love if this bug could get fixed!
Seeing the same. I'm in Firefox and it happens reliably when I enter visual select and then gg
or G
to jump to the top or bottom of the page. --bound line--
seems to be Wasavi's equivalent for --visual line--
, so I think the actual issue is that Wasavi freezes when using gg
or G
in bound line mode.
Played around with it a little more, it happens in both Firefox and Chrome, and seems to be related to the presence of consecutive lines. Doesn't occur if every line in the editor has content.
Happening to me as well. Would be nice to have some way to mitigate it, e.g. restarting wasavi without losing buffer contents.
EDIT: Was able to reproduce it by visual selection then typing j to extend it over an empty line. I just get "BOUND" as status and it freezes. By submitting the form I was still able to keep the textbox data up to the point where it crashed.
Mine just said "----BOUND----" or so, not sure how I managed to fall into it, but it was when I was deleting empty lines between two blocks using V to select multiple lines.
But yes: Locked up, aparently unrecoverably. Most painful.
I really love wasavi, but frequently I find it freezing, usually with the message "
--BOUND LINE--
" in the status area. When this happens, the only option seems to be reloading the page, which means I often lose the content of my text field.