Persistence.nvim isn't cooperating with neovide

[dusty-phillips]

I've been experimenting with Neovide (as one does periodically before inevitably reverting to the terminal) and it's becoming a compelling experience. I noticed that sessions are not getting saved correctly. This is at least partially due to the way Neovide sets itself up on Macos, so I'm not filing this as an issue on persistence.nvim, but I am seeking professional advice.

Context:

• I'm on a Mac (latest sequoia)
• Neovide (version 0.13.3) was installed with brew install neovide

If I run neovide from my terminal, neovide is opened with the CWD set to the folder that my terminal was in when I ran the command. If I run <leader>qq it closes and saves the session as expected, and <leader>qs restores the last session.

However, if I run Neovide.app from Macos Spotlight, it opens a neovide instance with the cwd set to /. I can use :cd to change the cwd, and <leader>qS allows me to select an old session that sets a different cwd. I can close the window with <leader>qq, but when I reopen it, <leader>qs doesn't do anything (at all; no error messages that I can find). If I use <leader>qS I can select the old session and it reflects whatever files were open when I called <leader>qq, so it is updating the session, just not loading it as the "last" session.

My best guess is one of these is happening:

• For some reason, it doesn't know to save an update to the current cwd as the "last" session, even though it is updating the "cwd" session.
• It is trying to load the last session, but refuses to do so because MacOS isn't allowing it to see into my home directory. Seems like <leader>qS also shouldn't work in this case, though.

---

As a workaround, I added S to my LazyVim dashboard to allow me to select session on startup:

return {
  "nvimdev/dashboard-nvim",
  opts = function(_, opts)
    table.insert(opts.config.center, 7, {
      action = function()
        require("persistence").select()
      end,
      desc = "Select Session",
      icon = "󰁯  ",
      key = "S",
      key_format = "  %s",
    })
  end,
}

I have no idea why the browser renders the icon like that; it's a refresh icon with a dot in the centre in neovim:

[rafaeloledo]

I'm not a professional session vimmer.

Recently, i was having problem with the BufReadPre default event that makes the plugin to not load on new folders that i've open, only when i open a file. Event if i set need to 0. I changed the plugin event to VimEnter and it always saves the session regardless of the situation. So, i don't need to hit <leader>qS to trigger the plugin setup function nor load a file to trigger BufReadPre.

I also use Neovide but on Windows. I've reproduced your described actions but it works fine here.

Remeber that vim have a differentiation between root_dir and cwd. Root dir is always the parent folder that vim is invoked. The cwd is the argument. cd seems to change the root_dir if i'm not mistaken, as i said, i'm not professional.

<leader>qs only restore the session state of saved dirs

Above you can see that it stores the directories.

So, i know that it can slow the vim loading

But i prefer always using <leader>qS to load AND change the directory rather than using zoxide which have the need of Alt-tabbing.

As you can see, the size of the file is negligible and i'm already fuzzy finding.

Look at vscode Ctrl+K, Ctrl+O shortcut, you need to click with mouse and navigate through explorer to reach the folder.

I just want the behavior that "if i've already visted the folder, it's being cached in the plugin to quickly jump to it"

I hope it can give some insight to your problem. But it seems not a problem with the plugin.