workspaces.nvim VS vim-obsession

`:tcd` into that project's folder. I'm using workspaces.nvim to create aliases for my project's folders, so I can simply do `:WorkspacesOpen MyProject`

workspaces.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.

i use workspaces for that, https://github.com/natecraddock/workspaces.nvim

I use https://github.com/natecraddock/workspaces.nvim and their compatible session manager. I have not tried the other two but workspaces works well and has done nice integrations (including telescope).

I use only one neovim instance and with the plugin https://github.com/natecraddock/workspaces.nvim I change between repositories.

I'm biased, but my favorite is a combination of workspaces.nvim and sessions.nvim (I created both). Both are extremely simple frameworks meant to be customized to your needs. Not for everyone, but if you are looking for something simple its worth giving a look.

workspaces.nvim

You must be talkng about pair programming, because that's the only situation where any of this stuff would actually matter. I haven't tried it out, but one possible solution is to just use a shared session file. You can use something like https://github.com/tpope/vim-obsession to keep it updated, and then you can decide on some heuristic to reload the session file (like on a timer, or in an autocommand).

obsssion

If you use Tim Pope's obsession, you can disable it right after closing your tab, then re-open your session. The tab you closed will still be here.

These are the main characteristics of linefly: * Small size (564 lines of Lua) * Very fast startup (almost as fast as the stock Neovim statusline) * Simple tab support (workspace tabs only, not buffer tabs) * Winbar support (works well in combination with global statusline) * Git branch detection * Git status via Gitsigns * Diagnostic status * vim-obsession and possession.nvim session support * Minimal jank as mode changes or write-status or line number changes; I don't like it when the filename moves one or two characters left or right when there are state changes. Not here. * Direct colorscheme support for these themes: moonfly, nightfly (both my own themes) along with: catppuccin, dracula, edge, embark, everforest, gruvbox,gruvbox-material, kanagawa, nightfox, sonokai and tokyonight. All other themes will use best-guess-fallback colors derived from the theme in effect.

Nice work, I may have to try this out. Currently I rely on vim-obsession and a bash function to open vim with a session file matching the name of the directory I'm in.

https://github.com/tpope/vim-obsession i like this one

Instead of a start screen, I prefer vim-obsession, Telescope, and which-key.nvim.

You might want to take a look at tpope’s obsession plugin https://github.com/tpope/vim-obsession