Closed dpetka2001 closed 4 months ago
Good catch. Fixed!
I also observe something similar in the .vim
files that are from session save/restore in the directory ~/.local/state/nvim/sessions
.
...azyVimDev/lazy/trouble.nvim/lua/trouble/view/section.lua:98: Error executing lua: ...VimDev/lazy/lualine.nvim/lua/lualine/utils/nvim_opts.lua:77: E539: Illegal character <j>
stack traceback:
[C]: in function 'nvim_win_set_option'
...VimDev/lazy/lualine.nvim/lua/lualine/utils/nvim_opts.lua:77: in function 'setter_fn'
...VimDev/lazy/lualine.nvim/lua/lualine/utils/nvim_opts.lua:50: in function 'set_opt'
...VimDev/lazy/lualine.nvim/lua/lualine/utils/nvim_opts.lua:74: in function 'set'
...local/share/LazyVimDev/lazy/lualine.nvim/lua/lualine.lua:432: in function 'refresh'
...l/share/LazyVimDev/lazy/trouble.nvim/lua/trouble/api.lua:150: in function 'on_update'
...azyVimDev/lazy/trouble.nvim/lua/trouble/view/section.lua:108: in function 'update'
...azyVimDev/lazy/trouble.nvim/lua/trouble/view/section.lua:72: in function 'finder'
...azyVimDev/lazy/trouble.nvim/lua/trouble/view/section.lua:66: in function 'fn'
...azyVimDev/lazy/trouble.nvim/lua/trouble/view/section.lua:99: in function <...azyVimDev/lazy/trouble.nvim/lua/trouble/view/section.lua:98>
[C]: in function 'nvim_win_call'
...azyVimDev/lazy/trouble.nvim/lua/trouble/view/section.lua:98: in function 'main_call'
...azyVimDev/lazy/trouble.nvim/lua/trouble/view/section.lua:64: in function 'fn'
.../share/LazyVimDev/lazy/trouble.nvim/lua/trouble/util.lua:119: in function <.../share/LazyVimDev/lazy/trouble.nvim/lua/trouble/util.lua:115>
[C]: in function 'xpcall'
.../share/LazyVimDev/lazy/trouble.nvim/lua/trouble/util.lua:115: in function <.../share/LazyVimDev/lazy/trouble.nvim/lua/trouble/util.lua:114>
I thought maybe it was the same error and it would be resolved if you fixed the one I mentioned in my OP, so that's why I didn't mention it before. Initially I thought it happened in vim files in general but I opened other vim files in ~/.local/share/nvim/lazy
and that didn't happen. This only happens in vim files that are from session save/restore. For now I just disable the specific component in my config. Of course it's not something major as when skimming through code like in my OP.
It's the escaping of %
characters that still fails.
Can be easily reproduced with for example: nvim foo%j.txt
.
Will further look into this.
hmm, it seems that I can trigger the same issue even without trouble
It seems that LazyVim's pretty path triggered the same issue. Fixed it in LazyVim
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.10.0-dev-3078+g3a8265266
Operating system/version
Linux Mint 21.3
Describe the bug
When I was trying to skim through some of
lazy.nvim
's code today in my locally forked repo, when i went on this line, I got the following errorSteps To Reproduce
lazy.nvim
repo locallyExpected Behavior
No error
Repro