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

Single-line comment in javascript file gets evaluated as vim regular expression. #1432

Closed
Remich opened this issue Feb 10, 2023 · 0 comments
Closed

Comments

@Remich
Copy link

Remich commented Feb 10, 2023

Problem: When writing a single-line comment at the beginning of a line (e.g. // foobar) in a javascript file the following error message appears:

Error detected while processing TextChangedI Autocommands for "*":
E35: No previous regular expression

As far as I know the // can be used inside some vim commands to refer to the previous search term or the previous regular expression.
It looks to me like some string is not being properly escaped.
I already looked into the source code, but could not fix it. Because I don't know where exactly the issue occurs.

Disabling nvim-cmp resolves the issue.

People over here might have the same issue: quangnguyen30192/cmp-nvim-ultisnips#80

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

No branches or pull requests

2 participants