cmp-cmdline icon indicating copy to clipboard operation
cmp-cmdline copied to clipboard

init.lua:35: couldn't parse regex

Open Tej12345 opened this issue 1 year ago • 3 comments

Error detected while processing /home/tejpapa/.local/share/nvim/site/pack/packer/start/cmp-cmdline/after/plugin/cmp_cmdline.lua: E5113: Error while calling lua chunk: ...e/pack/packer/start/cmp-cmdline/lua/cmp_cmdline/init.lua:35: couldn't parse regex: Vim:E369: invalid item in %[] stack traceback: [C]: in function 'create_regex' ...e/pack/packer/start/cmp-cmdline/lua/cmp_cmdline/init.lua:35: in main chunk [C]: in function 'require' ...ck/packer/start/cmp-cmdline/after/plugin/cmp_cmdline.lua:1: in main chunk

Tej12345 avatar Apr 12 '23 15:04 Tej12345

I am also facing this issue.

2023-06-09T19:07:03 lazy.nvim  ERROR Failed to source `/home/lenovo/.local/share/nvim/lazy/cmp-cmdline/after/plugin/cmp_cmdline.lua`

vim/_editor.lua:0: User Autocommands for "VeryLazy"..script nvim_exec2() called at User Autocommands for "VeryLazy":0../home/lenovo/.local/share/nvim/lazy/cmp-cmdline/after/plugin/cmp_cmdline.lua: Vim(source):E5113: Error while calling lua chunk: ...cal/share/nvim/lazy/cmp-cmdline/lua/cmp_cmdline/init.lua:38: couldn't parse regex: Vim:E369: Invalid item in \%[]
stack traceback:
	[C]: in function 'create_regex'
	...cal/share/nvim/lazy/cmp-cmdline/lua/cmp_cmdline/init.lua:38: in main chunk
	[C]: in function 'require'
	...share/nvim/lazy/cmp-cmdline/after/plugin/cmp_cmdline.lua:1: in main chunk
	[C]: in function 'nvim_exec2'
	vim/_editor.lua: in function 'cmd'
	...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:473: in function <...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:472>
	[C]: in function 'xpcall'
	.../.local/share/nvim/lazy/lazy.nvim/lua/lazy/core/util.lua:110: in function 'try'
	...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:472: in function 'source'
	...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:431: in function 'source_runtime'
	...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:402: in function 'packadd'
	...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:335: in function '_load'
	...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:184: in function 'load'
	...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:331: in function <...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:330>
	[C]: in function 'xpcall'
	.../.local/share/nvim/lazy/lazy.nvim/lua/lazy/core/util.lua:110: in function 'try'
	...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:330: in function '_load'
	...local/share/nvim/lazy/lazy.nvim/lua/lazy/core/loader.lua:184: in function 'load'
	...hare/nvim/lazy/lazy.nvim/lua/lazy/core/handler/event.lua:33: in function <...hare/nvim/lazy/lazy.nvim/lua/lazy/core/handler/event.lua:26>
	[C]: in function 'nvim_exec_autocmds'
	.../.local/share/nvim/lazy/lazy.nvim/lua/lazy/core/util.lua:149: in function <.../.local/share/nvim/lazy/lazy.nvim/lua/lazy/core/util.lua:144>

# stacktrace:
  - vim/_editor.lua:0 _in_ **cmd**

lalitmeeq avatar May 26 '23 17:05 lalitmeeq

can confirm this issue occured after https://github.com/hrsh7th/cmp-cmdline/commit/79456dc113afe8420e08e31f0bb55dfe0eb45903, and only happened with set regexpengine=1

can simply reproduce by add set regexpengine=1 in vimrc, then start vim

image

Hi @hrsh7th, could you help looking this?

jiz4oh avatar Jun 29 '23 07:06 jiz4oh

I faced same issue.

E5113: Error while calling lua chunk: ...e/pack/packer/start/cmp-cmdline/lua/cmp_cmdline/init.lua:38: couldn't parse regex: Vim:E369: Invalid item in \%[]
stack traceback:
        [C]: in function 'create_regex'
        ...e/pack/packer/start/cmp-cmdline/lua/cmp_cmdline/init.lua:38: in main chunk
        [C]: in function 'require'
        ...ck/packer/start/cmp-cmdline/after/plugin/cmp_cmdline.lua:1: in main chunk

As @jiz4oh said, when I add the vimscript below (for 'Far' plugin), this happens.

set regexpengine=1        " Error occurs.

And if I remove or comment out this line, the error goes away.

" set regexpengine=1        " Error goes away.

Is this the only solution ?

Thank you.

riodelphino avatar Aug 06 '23 16:08 riodelphino