Why is vim.g.persisting not set on load ?

[dca123]

I installed the plugin with lazy as such.

	{
		"olimorris/persisted.nvim",
		config = true,
		lazy = true,
	},

Then in .config/nvim/after/plugin/persisted.lua, I loaded the telescope extension as such

require("telescope").load_extension("persisted")

vim.keymap.set("n", "<leader>ps", ":Telescope persisted<CR>", {})

My autosave (by default) feature was not working. The rest of the plugin worked perfectly as I could use :SessionSave and :SessionLoad to load up the sessions. After some investigating, I discovered that vim.g.persisting was not set. Manually setting this to true as shown below, enabled the autosave feature.

require("telescope").load_extension("persisted")


vim.g.persisting = true
vim.keymap.set("n", "<leader>ps", ":Telescope persisted<CR>", {})

Any idea why this might be happening ?

Cheers !

[olimorris]

It's because you've set lazy = true

[dca123]

Thank you for your response !

Tried it with removing lazy = true and then removing the vim.g.persisting = true.
Unfortunately the issue exists and vim confirms with Undefined variable: g:persisting

[dca123]

My assumption is that the session doesn't automatically start. After playing around a bit more, I noticed that running :SessionStart will setup the global variable and everything works as expected.

[olimorris]

So lazy = true will stop the plugin from starting so if you run :lua print(vim.g.persisting) you'll see nil.

If you start looking at the code from here you'll see how this happens.

[dca123]

So I tried with both lazy = false, and lazy removed, both with :lua print(vim.g.persisting) resulting in nil.

I also looked into the function and manually added

"olimorris/persisted.nvim",
config = true,
opts = {
			autosave = true,
			allowed_dirs = nil,
			ignored_dirs = nil,
		},

in hope that this might allow the function to succeed - alas no luck

[dca123]

Good news ! I had no idea what 'vim.fn.argc()' this does. Looked up the man files, and it's looking at the arguments. I've aliased my neovim as n = nvim . and it seems this is the culprit 🤣

All good now, working as intended ! Thanks for linking the code - I wouldn't have found this by myself

Do you typically open up nvim with just 'nvim' as opposed to 'nvim .' ? I just switched from vscode a few days ago, and I used to do 'code .' to open up code in my cwd, so I just carried it over.

[olimorris]

Fantastic spot! That's one of those issues that could have taken ages to find 😄 .

My alias is nv and I have a Fish function:

function nv -d "Launch Neovim"
    if count $argv >/dev/null
        nvim $argv
    else
        nvim
    end
end

So it launches Neovim with nv and what ever other arguments I pass to it.

[RazaGR]

I encountered the same issue when I use nvim . (with dot) it doesn't autosave new changes,
@olimorris is there any solution for that so we can autosave with nvim . `?
🙏