bug: Line numbers disappear when restoring session

[joebonneau]

Did you check docs and existing issues?

• [X] I have read all the persistence.nvim docs
• [X] I have searched the existing issues of persistence.nvim
• [X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.9.2

Operating system/version

MacOS 13.6

Describe the bug

Using the default configuration for persistence.nvim that lazyvim ships with

When I restore a session, the line numbers (in this case, I'm using relative numbers) disappear. They do not return if I try to run :set relativenumber or :set number. The only way that I'm able to get them back is to close nvim and reopen the files manually.

Thanks in advance!

Steps To Reproduce

1. Open at least one buffer
2. Close nvim
3. Reopen nvim and restore the last session

Expected Behavior

line numbers will appear as they did in the previous sessionk

Repro

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy.nvim, LazyVim and your plugins
require("config.lazy")

[folke]

There was an issue with LazyVim's new news feature. Whenever news was shown, it messed up some global options. This has been fixed somewhere yesterday, but your existing sessions might still be wrong.

Try with opening NEovim, open some files, restart and load the session. Line numbers should work again as normal.

[joebonneau]

Hi @folke - thanks for the quick response. I tried the approach you suggested and I'm still not seeing any line numbers after restoring the session.

I took a quick video of what it looks like (apparently asciinema doesn't like nerd font symbols): https://asciinema.org/a/MV8VD3IXKVQof91KBTmiexNbm

[folke]

I can't reproduce this at all.

Have you tried with a fresh starter?

[joebonneau]

Just tried cloning the fresh starter and adding my config back in and the issue is still there. I'm wondering if there's some weird interaction with how I have things configured, but I'm certainly not going to ask you to pick through it to find a cause 😄

I'll keep at it and let you know if I manage to figure it out. Thanks for the help so far.