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
I have searched the exsiting issues of plugins related to this issue
Neovim version (nvim -v)
NVIM v0.8.2
Operating system/version
MacOS 11.5
Describe the bug
The latest version of LazyVim no longer displays the line numbers to the left of the buffer when opening a file directly from the terminal.
Steps To Reproduce
Go to a directory in the terminal
vim filename directly
There are no line numbers on the left
Expected Behavior
Line numbers would be on the left, just like they are if you open vim and then open a file from within vim.
Repro
-- DO NOT change the paths and don't remove the colorschemelocalroot=vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .reprofor_, nameinipairs({ "config", "data", "state", "cache" }) dovim.env[("XDG_%s_HOME"):format(name:upper())] =root.."/" ..nameend-- bootstrap lazylocallazypath=root.."/plugins/lazy.nvim"ifnotvim.loop.fs_stat(lazypath) thenvim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
endvim.opt.runtimepath:prepend(lazypath)
-- install pluginslocalplugins= {
"folke/tokyonight.nvim",
"folke/LazyVim",
-- add any other plugins here
}
require("lazy").setup(plugins, {
root=root.."/plugins",
})
vim.cmd.colorscheme("tokyonight")
-- add anything else here
The text was updated successfully, but these errors were encountered:
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.8.2
Operating system/version
MacOS 11.5
Describe the bug
The latest version of LazyVim no longer displays the line numbers to the left of the buffer when opening a file directly from the terminal.
Steps To Reproduce
vim filename
directlyExpected Behavior
Line numbers would be on the left, just like they are if you open vim and then open a file from within vim.
Repro
The text was updated successfully, but these errors were encountered: