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
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.
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: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
The text was updated successfully, but these errors were encountered: