lh-brackets won't work in nvim

[at8i]

Describe the bug
A clear and concise description of what the bug is.
After installing these two plugins, an error message popped up which prevented the plugin to work properly.

vim/_editor.lua:0: /Users/at8i/.config/nvim/init.lua..nvim_exec2() called at /Users/at8i/.config/nvim/init.lua:0../Users/at8i/.local/share/nvim/lazy/lh-brackets/plugin/bracketing.base.vim[196]..
function lh#mapping#plug[33]..
<SNR>20_callsite[1]..lh#exception#get_callstack[4]..lh#exception#decode[2]
..lh#exception#callstack[61]..lh#askvim#where_is_function_defined[13]..lh#askvim#execute, line 1: Vim(function):E123: Undefined function: 0

# stacktrace:
  - vim/_editor.lua:0 _in_ **cmd**
  - ~/.config/nvim/init.lua:19

And also when I press ", it prints out the following;

""<Plug>MarkersInsertMark

To Reproduce
Steps to reproduce the behavior:

1. Go to your init file and install lh-brackets and lh-vim-lib
2. Installing these two plugins using lazynvim plugin manger and setting lh-vim-lib as a dependency for lh-brackets
3. Starting nvim with any file will cause the above error to pop out.

** Context (please complete the following information):**

• nvim v0.9.0

[LucHermitte]

I'm not sure why you observe these errors. I've just used nvim 0.9 (from snap) with my .vimrc as parameter, and "unfortunately" I did not observe your errors.

In doubt, I've updated two lines in lh-brackets and lh-vim-lib.: the syntax of has('patch-') was more permissive in the past.

[at8i]

Hello ,
I have updated the plugins but with no luck. Same error persists. These are the things I have done so far.
1- I installed all of your plugins to see if the function call can be traced but the same error exists. And also these are some of the other errors that came from other ones:

2023-05-17T14:21:12 lazy.nvim  ERROR  | lazy.nvim: Failed to source `/Users/at8i/.local/share/nvim/lazy/searchInRuntime/plugin/searchInRuntime.vim`

vim/_editor.lua:0: /Users/at8i/.config/nvim/init.lua..nvim_exec2() called at /Users/at8i/.config/nvim/init.lua:0../Users/at8i/.local/share/nvim/lazy/searchInRuntime/plugin/searchInRuntime.vim, line 226: Vim(let):E117: Unknown function: lh#option#get_non_empty

# stacktrace:
  - vim/_editor.lua:0 _in_ **cmd**
  - ~/.config/nvim/init.lua:19
2023-05-17T14:21:12 lazy.nvim  ERROR  | lazy.nvim: Failed to source `/Users/at8i/.local/share/nvim/lazy/lh-tags/plugin/lh-tags.vim`

vim/_editor.lua:0: /Users/at8i/.config/nvim/init.lua..nvim_exec2() called at /Users/at8i/.config/nvim/init.lua:0../Users/at8i/.local/share/nvim/lazy/lh-tags/plugin/lh-tags.vim, line 141: Vim(call):E117: Unknown function: lh#project#menu#make

# stacktrace:
  - vim/_editor.lua:0 _in_ **cmd**
  - ~/.config/nvim/init.lua:19
2023-05-17T14:21:12 lazy.nvim  ERROR  | lazy.nvim: Failed to source `/Users/at8i/.local/share/nvim/lazy/lh-brackets/plugin/bracketing.base.vim`

vim/_editor.lua:0: /Users/at8i/.config/nvim/init.lua..nvim_exec2() called at /Users/at8i/.config/nvim/init.lua:0../Users/at8i/.local/share/nvim/lazy/lh-brackets/plugin/bracketing.base.vim[196]..function lh#mapping#plug[33]..<SNR>32_callsite[1]..lh#exception#get_callstack[4]..lh#exception#decode[2]..lh#exception#callstack[61]..lh#askvim#where_is_function_defined[13]..lh#askvim#execute, line 1: Vim(function):E123: Undefined function: 0

# stacktrace:
  - vim/_editor.lua:0 _in_ **cmd**
  - ~/.config/nvim/init.lua:19

I got these errors too.

What I plan to do is:
1- Try a fresh nvim config with lazynvim to see if there is some sort of problem with your plugins and lazynvim plugin manager.
2- If lazynvim can load your plugins without any problem then it means my current setup is problematic.
3- If problem persists after fresh install it means lazynvim can not load your plugins then I will try vim-plug manager to see if it fixes it.

I will let you know tonight or tomorrow night. Thank you for all the awesome plugins. <3

[at8i]

Hello again,
Seems that it has something to do with my setup. I was able to fix it with a clean vim setup.

[LucHermitte]

Sorry I did not had much time to have a look into it.
Looks like a configuration error related to how my plugins are registered in your plugin manager -- the error about lh-tags (another plugin of mine) was strange.

Any way. Can we close this issue if everything is fine now?