vim-projectionist VS vim-vinegar

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.

I just recently got into the "plugin frenzy", and since I was already using netrw, I ignored all the tree-style options and just installed the tpope's vim-vinegar to extend it.

Netrw + vim-vinegar works for me. In conjunction with harpoon and a bufferline and maybe vim-eunuch, it works out pretty well

I think you might be looking for netrw (:Ex brings it up). It is the default file explorer and can be used in many cool ways. There are extensions for it, like (vim-vinegar, and :help netrw is your friend :)

Plain `netrw` with a few options changed and tpope's vim-vinegar for easy access

I use Vinegar but should try Oil. https://github.com/tpope/vim-vinegar

Hijacking netrw to prevent disruptive "project drawer" style plugins as mentioned in the vim-vinegar readme is important to me.

When you understand the default file explorer, you'll probably appreciate https://github.com/tpope/vim-vinegar

ThePrimeagen suggests pv as the mapping to see the folder, but - comes from me being used to https://github.com/tpope/vim-vinegar some time ago. Choose your's to your liking.

Netrw, vim’s built in file explorer is pretty solid if you’re looking to understand the topology of a project. I really like the pattern of browsing the file tree in the window pane where the file will open. vim vinegar is a great plugin for refining the netrw experience and making it a little more seamless. Takes a minute to learn the keybindings, but I find it much lighter and less intrusive than nerd tree or it’s offshoots.

This one is for the vinegar workflow enjoyers. Netrw is good enough for my needs but it was missing a bit of *bling*. This plugins adds basic icon supports and custom keymappings.