vim-projectionist VS vim-obsession

Tim Pope's projectionist for navigating to files of a particular category or to related files from the current one: https://github.com/tpope/vim-projectionist.

> For myself, I'm fine with the typing being in a separate .rbs file

We type[0] by having one separate .rbs file per .rb file. Works really well with an editor's vertical splits: type outline on one side, code on the other. That, or use something like vim-projectionist[1].

[0]: (WIP: there's a huge codebase to type, but we're progressively getting there) https://github.com/DataDog/dd-trace-rb/tree/master/sig

[1]: https://github.com/tpope/vim-projectionist

One of the originals I guess must be tim pope's https://github.com/tpope/vim-projectionist

use https://github.com/tpope/vim-projectionist - define the relationships between files (example: app/*js are 'source' files and test/*js are 'test' files). Projectionist sets up `:A` to jump to the 'alternate' file (jump between a 'source' file and its 'test' for instance), and `:Esource` and `:Etest` commands to find/navigate by the kind of file. This is very powerful IMO - for projects with good structure I can quickly jump between related test/source/model/blah files very quickly using these commands. For projects without good structure I rethink or get the team to talk about how we might improve the project organization (ie, lack of structure is a code smell!)

I love Tpope’s https://github.com/tpope/vim-projectionist but this one seems like a great replacement 😎

Tim Pope's excellent Projectionist plug-in has an alternate file feature, which makes it very easy to switch between test and implementation files.

The plugin is inspired by vim-projectionist and https://github.com/vim-scripts/a.vim

This feels like a bug, since the plugin doesn't behave as expected when following the installation section verbatim. I filed a bug here: https://github.com/tpope/vim-projectionist/issues/168

You need https://github.com/tpope/vim-projectionist. Gotta have a file structure for unit tests though.

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