zsh-z VS vim-projectionist

I think that covers your description, and a great folder jumping plugin is zsh-z.

I'll just add that if you ever have a reason to try an alternative to zoxide, I've been very happy with zsh-z.

If you're interested in these types of things take a look at https://github.com/agkozak/zsh-z or https://github.com/wting/autojump

It has radically improved my workflow in the same way that zsh-z did for me a couple years ago: it reduces the cognitive load of having to remember where things are.

zshell-z Even simpler and more flexible.

z to jump to recent directories

if you are using zsh try https://github.com/agkozak/zsh-z

git clone https://github.com/agkozak/zsh-z ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-z

z (https://github.com/agkozak/zsh-z), similar to cdr but scores EVERY directory you ever gone into, to sort by frecency (mix of frequency & recency), paired to fzf it's a beast to navigate to a directory (I hardly ever use cd to traverse directories nowadays)

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.