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
Trying to replace something in yaml file, I get this error,
E5108: Error executing lua: /home/ds/.local/share/nvim/lazy/ssr.nvim/lua/ssr/search.lua:206: Invalid 'end_row': out of range
stack traceback:
[C]: in function 'nvim_buf_set_text'
/home/ds/.local/share/nvim/lazy/ssr.nvim/lua/ssr/search.lua:206: in function 'replace'
/home/ds/.local/share/nvim/lazy/ssr.nvim/lua/ssr.lua:284: in function 'func'
/home/ds/.local/share/nvim/lazy/ssr.nvim/lua/ssr.lua:106: in function </home/ds/.local/share/nvim/lazy/ssr.nvim/lua/ssr.lua:105>
NVIM v0.10.0-dev-2315+g32b49448b
Build type: RelWithDebInfo
LuaJIT 2.1.1707061634
Compilation: /usr/bin/gcc-10 -O2 -g -Og -g -flto=auto -fno-fat-lto-objects -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes
-std=gnu99 -Wshadow -Wconversion -Wvla -Wdouble-promotion -Wmissing-noreturn -Wmissing-format-attribute -Wmissing-prototypes -fsigned-char -fstack-protector-strong -fno-common -Wno-unused-result -Wimplicit-fallthrough -fdiagnostics-color=always -DUNIT_TESTING -DHAVE_UNIBILIUM -D_GNU_SOURCE -DINCLUDE_GENERATED_DECLARATIONS -I/home/runner/work/neovim/neovim/.deps/usr/include/luajit-2.1 -I/home/runner/work/neovim/neovim/.deps/usr/include -I/home/runner/work/neovim/neovim/build/src/nvim/auto -I/home/runner/work/neovim/neovim/build/include -I/home/runner/work/neovim/neovim/build/cmake.config -I/home/runner/work/neovim/neovim/src -I/usr/include
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/usr/local/share/nvim"
Run :checkhealth for more info
● ssr.nvim 0.05ms start
dir /home/ds/.local/share/nvim/lazy/ssr.nvim
url https://github.com/cshuaimin/ssr.nvim
branch main
commit bb323ba
readme README.md
The text was updated successfully, but these errors were encountered:
Trying to replace something in yaml file, I get this error,
The text was updated successfully, but these errors were encountered: