vim-obsession VS mini.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

This is essentially a tagline of mini.move.

Just as the others suggested, oil.nvim solves this outta the box. I freaking love it (here my config in case ya need it). Apparently also mini.files handles this by default

You mean backwards seeking text objects? You can get those with mini.ai https://github.com/echasnovski/mini.nvim/blob/main/readmes/mini-ai.md

I would like to offer you to join me in saying late greetings to this autumn with a release of mini.nvim version 0.10.0. It is mostly about introducing three (quite feature full, dare I say) modules and minor updates of existing ones.

Last night I cleaned up all the dead code in my config and realised that mini.nvim has to be the single best plugin that I've used. I have a couple of other favourites but this collection has been so consistently good that I wanted to give some thanks to the juggernaut that is u/echasnovski! Thanks for all the work you plugin authors and core maintainers put in to make this editor what it is <3

For example: I spent a lot of time configuring file tree plugins to have the same sorting as VS Code, tweaking their icons, etc. But then I realized I barely used the file explorer at all, and now I'm super happy with the minimal approach of mini.files. I had similar experiences with other plugins that were just adding "fluff" instead of the functionality I was looking for.

Around two weeks ago I've announced the release of mini.files - a file explorer module of mini.nvim with column view navigation and "edit text to manipulate file system" design. This resulted into a great feedback from the community, much of which turned into new features.

A mini.ai textobject specification that you can use standalone