persistence.nvim VS telescope-project.nvim

persistence.nvim for using session management which is useful

i use persistence.nvim plugin, and i map the commands on my dashboard so i can open my last session

I've been using vim sessions for a while now. Sessions can have their own configuration files and that's what I use for projects. For this to be actually convenient you'll need plugin like persistence.nvim to handle the sessions themselves (or make your own workflow).

I like the idea of a "config" module. Plugins like persistence and mason.nvim have it, they allow you to set variables without calling the main module.

persistence.nvim: Small session manager. I use some of its functions to also manage project local configs. It is because of this plugin I can use language servers the way I want.

persistence.nvim * Automatically save active session to a configurable directory * API to load most recent or current session based on cwd * No direct support for a telescope picker but could probably be setup with vim.ui.select()

yeah, I was planning on shimming this functionality out to another plugin. sessions have little to do with a startup gui imo. i mention in the docs using something like https://github.com/folke/persistence.nvim

Projects are handle by the telescope-project plugin (https://github.com/nvim-telescope/telescope-project.nvim) Does is change when you open folder by its name ? With “lvim .” ? With just “lvim” ?

I found this plugin for telescope that does all of the above, except that it requires a redundant step where even though I'm inside a project, I still have to select the project before I can search / grep inside. Basically, I want to create a mapping that allows me to search inside the project without having to always select the project that I am in (it should be able to detect that the file from which I am searching belongs to such-and-such project and so can instantly search from within that project).

telescope-project.nvim

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.

This seems to be a https://github.com/nvim-telescope/telescope-project.nvim

Few months ago I tried https://github.com/nvim-telescope/telescope-project.nvim but it does not restore windows layout (seem to only cd into project dir). Are there any other session managers that support features listed above?

Anyhow, I started clearing the last requirements standing by installing telescope-project.nvim and todo-comments.nvim. They were a convenient choice, as both extend the already mentioned Telescope plugin. Seamless terminal integration was possibly the feature I was looking for the most. As I hoped, Neovim offers transparent terminal emulation out of the box, making to open a terminal buffer feel like a first class operation.

To be fair, there is telescope-project, which almost does what I'm looking for. The only drawback for me is, that I want a command, that I can call with a single keystroke. telescope-project always shows a list of all registered projects and you have to select the first one, which adds friction to the editing-flow.