-
-
Notifications
You must be signed in to change notification settings - Fork 109
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
Cannot evaluate regex #143
Comments
Hmm I'll investigate! Not sure why this would happen, Conjure doesn't care about the code, it just grabs strings and sends them off to the nREPL, so it's probably something surprising and maybe unrelated to Conjure but worth getting to the bottom to. |
Oh yeah, I can repro! I have a hunch it's to do with the paren matching / searching, I think I need to add a special case for regex that contain parens like I do strings. I thought they'd be under the same part of the nvim syntax tree but I guess not! |
We don't want to count parens within regular expressions, some syntax files seem to define this as Regex and some as Regexp, I think. Haven't confirmed that and I probably should.
Should be alleviated / fixed on |
It still behaves weird if you try to eval from within the parens inside the regex, maybe that can be improved, although I think this allows you to eval commented out forms if you need to, which is kinda useful? |
Thanks for the fast response! I will give the |
Closing because I think this should be enough for now, further improvements to not getting confused by parens in strings will come with tree-sitter soon (tm). |
I encountered a strange bug with some regex.
When trying to evaluate the following form, I get no result, nor any logs.
Note: When selecting the line in visual mode and pressing
\E
I get a result.I'm running neovim 0.4.4 and conjure 4.9.0
The text was updated successfully, but these errors were encountered: