auto-session VS neovim-session-manager

The plugins are: https://github.com/goolord/alpha-nvim and https://github.com/rmagatti/auto-session

I use auto-session for session management and session-lens telescope extension for switching the sessions. When I switch to a different session, auto-session clears all buffers from my current session, including the modified ones, without warning. I'm wondering if there are any ways to prevent losing my changes. For instance, can I save the modified buffers in the session and load them on session restore, or configure auto-session to give me a warning before switching to a new session if there are unsaved changes? Alternatively, is there a way to use Telescope to display a list of recently modified buffers, so that I can review them before switching sessions and take appropriate action?

buffers: I open and close nvim instances all day long, using https://github.com/rmagatti/auto-session (or one of the many other session management plugins), it saves my buffers on a per git branch basis, so I lose nothing. nvim opens in less than a second, so this is no burden at all.

Yes, I use rmagatti/auto-session with some gnarly hacks to save a subset of window options, a per-session colorscheme, and some other wacky stuff so it stays 99.9% the same between sessions.

The correct one is : auto-session (I edited the mistake in the message above)

auto-session ?

I'm also using auto-session and nvim-tree which can both interact with the session.

Finally, to save sessions and move through them, check: auto-session

Yes, for this purpose, I'm using rmagatti/auto-session

I use neovim-session-manager, for my needs, works pretty well! :)

I have a question about https://github.com/Shatur/neovim-session-manager How do I make it so the session doesn't autoload, but it still autosaves?

Something that is a bit more advanced, which I'll just throw out there to let you know exists, is sessions. It basically saves all the currently open buffers, tabs, panes, and how they're set up so you can return to them later. You can use them without plugins and open, load, and save them manually, or you can use a session manager (I personally use Neovim-session-manager). That way if you're working on a project for class X, you can save the session, close Neovim or open another session to work on class Y, and you can return to that session whenever you want.

Personally I use neovim-session-manager for this (https://github.com/Shatur/neovim-session-manager) and haven't had any complaints with it so far.

I use AstroNvim which utilizes https://github.com/Shatur/neovim-session-manager to jump between “projects”. You can then save a “project” and find/go to previously saved “projects” and it will cd for you.

Shatur/neovim-session-manager: A simple wrapper around :mksession.

Sharing a lightweight plugin I wrote yesterday which provides some functions for accessing previously used current working directories. I know that this is similar to some other "workspace" / "project" plugins which already exist, so I've pasted the motivation section from the README. >I work in a large monorepo and change my working directory depending on what part of the codebase I'm looking at to give my LSP (gopls) a chance and to improve the usefulness of fuzzy finding files. I want to change the current working directory back to a previously used one without having to configure a "project" or "workspace" beforehand. This requirement is not satisfied (as far as I can tell) by existing similar plugins: > - project.nvim > - telescope-project.nvim > - workspaces.nvim. > - neovim-session-manager > olddirs.nvim is very lightweight and doesn't provide any niceties (out of the box) like some of the above plugins, it's literally just :oldfiles for directories. > \ I say "out of the box" since some features like the searching or browsing of files inside a previous directory can be implemented by adding actions to the olddirs.nvim Telescope picker.

You could take a look at this one: https://github.com/Shatur/neovim-session-manager

Have you tried neovim-session-manager?

You can use a session manager so it would be easy to just quit and reload the last session, at least, this is what I'm doing.