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
{{ message }}
This repository has been archived by the owner on Oct 21, 2022. It is now read-only.
There are other weird behaviors that seem related but I can't remember the details off the top of my head. I'll update this issue when I re-encounter them.
The text was updated successfully, but these errors were encountered:
+1
Thank you kenny-evitt for tagging me on this. I have the same mark up showing in my status bar as well when I initially start up LT and use any vim command besides h,j,k,l.
I did notice that when I go into either user keybindings/behaviors and make a change i.e. make a new line and save, everything related to vim works. That being said, I have no idea where to start to debug the problem. Hope this helps people smarter than me ;).
thanks for the tip, tgfbikes! i wonder how long til the issue resurfaces...
edit: i've noticed that 'change (c)' doesn't go into insert mode now! haha. so either find and : are broken, or change is broken. very strange things are going on. and apparently a friend can't enter insert mode now at all, nor use :, but find does work. good luck to whoever debugs this
edit2: another bug: hitting escape does not leave insert mode. you have to hit it twice to get out. this together with the change bug makes it seem like it's sitting in a mode where it refuses a mode change at least once. ie. change tries to insert but can't so a 2nd explicit insert is needed; escape tries to leave the current mode but can't so a 2nd escape is needed. ctrl-c works properly however to leave a mode immediately
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This comment reminded me of this issue.
Steps to reproduce:
There are other weird behaviors that seem related but I can't remember the details off the top of my head. I'll update this issue when I re-encounter them.
The text was updated successfully, but these errors were encountered: