z VS vim-projectionist

https://github.com/skywind3000/z.lua was another that I used for a long time, although I've lately started using https://github.com/jethrokuan/z

A lot of reinventing the wheel in the z space it seems

z

Fish + Starship (https://starship.rs/) + z (https://github.com/jethrokuan/z). For me it is a really nice configuration, fast do do stuff & visually pleasant (it influences my comfort & motivation).

I use fish shell with z plugin to quickly jump to directories and nnn file manager mainly to select files for deletion. I also use dirbuf plugin for neovim when working inside this editor.

it also has a fish version https://github.com/jethrokuan/z

Use a directory jumper, so you don't have to keep cding all the time. I use z

https://github.com/jethrokuan/z Looks like it exists for fish, too

z for fish - Directory jumping

That reminds me of the fish z port...it does some fuzzy matching to get you quickly to frequently used dirs

Been using https://github.com/jethrokuan/z for a long time but yours looks nice! I'll definitely take a look at your search system.

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.