-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STRING with more than one word is not treated properly as ELEMENT with the motion commands #33
Comments
@nimaai Thanks for reporting. I've confirmed the issue, and will post an update once I've had a chance to root-cause... |
and also (not sure if this is related) when pressing correct:
but what happens is following:
|
@nimaai Interestingly, I've been able to reproduce the original issue only in the terminal. Have you tried this in gvim or only in a terminal? |
@bpstahlman i am using terminal neovim and gui neovide. same issues in both environments. |
@nimaai Which version of neovim? I see the original problem you reported in Vim 8.1, but not in Vim 8.2, so I want to be sure I'm using the same version of neovim. |
Also, can you tell me the version/commit of both vim-sexp and whatever lisp syntax file you're using? The latter may be significant because the only time I was able to reproduce the issue, it occurred because the string wasn't being highlighted properly, and vim-sexp uses the synstack to delineate the elements. I don't see the issue on neovim 0.6.1. So far, I've seen it only on Vim 8.1. |
same problem with |
I'm not able to reproduce either issue with the versions you mentioned. The only other variable that seems potentially relevant is the terminal itself. I would expect this to matter more with Vim than Neovim. For instance, in my current terminal, Vim will treat a |
@bpstahlman iterm Build 3.5.10 |
starting at
f
jumps properly with<M-w>
jumps inside the string with
<M-w>
same behaviour with
<M-b>
from my point of view this is an incorrect behaviour and it was not working like this in the past.
The text was updated successfully, but these errors were encountered: