Skip to content
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

Open
nimaai opened this issue Nov 5, 2024 · 9 comments

Comments

@nimaai
Copy link

nimaai commented Nov 5, 2024

(foo "bar" :baz)
 ^   ^     ^

starting at f jumps properly with <M-w>

(foo "bar qux" :baz)
 ^   ^    ^    ^

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.

@bpstahlman
Copy link
Collaborator

@nimaai Thanks for reporting. I've confirmed the issue, and will post an update once I've had a chance to root-cause...

@nimaai
Copy link
Author

nimaai commented Nov 12, 2024

and also (not sure if this is related) when pressing " inside the string at the end i would expect this plugin to just "jump over" in order to maintain the balanced closing ".

correct:

"foo bar"
       ^
 -->
 "foo bar"
          ^

but what happens is following:

"foo bar"
       ^
 -->
 "foo bar "" "
          ^

@bpstahlman
Copy link
Collaborator

@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?

@nimaai
Copy link
Author

nimaai commented Nov 13, 2024

@bpstahlman i am using terminal neovim and gui neovide. same issues in both environments.

@bpstahlman
Copy link
Collaborator

@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.

@bpstahlman
Copy link
Collaborator

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.

@nimaai
Copy link
Author

nimaai commented Nov 19, 2024

@bpstahlman

neovim v0.10.2
vim-sexp 14464d4
clojure.vim 128ccd4

same problem with vim-racket dcfb8c1.

@bpstahlman
Copy link
Collaborator

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 <M-w> like a simple w if I don't have a set <M-w>=^[w in my vimrc. IIUC, Neovim handles that sort of thing transparently, with no need for special termcap sets. But just in case, which terminal are you using?

@nimaai
Copy link
Author

nimaai commented Nov 22, 2024

@bpstahlman iterm Build 3.5.10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants