vim-projectionist VS ranger

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.

Came to post zoxide. Also if you use `ranger`[1] (vim inspired file manager) then you might like to add the `ranger-zoxide` plugin[2].

1. https://github.com/ranger/ranger

2. https://github.com/jchook/ranger-zoxide

This looks cool, though I already use https://github.com/ranger/ranger for this.

This feature is rarely seen in Linux file managers. I would recommend the CLI file manager ranger. If you need a GUI tool, you should have a look at pantheon files, the file manager of ElementaryOS.

Someone opened an issue about this. Might want to follow that.

Hi! I am using ranger file manager terminal as its best through all i had used, but i have a weird problem and i want to ask you maybe you know how to solve it because my knowledge have limits on this topic even though i researched a bit.

How about ranger

I wrote a ranger integration plugin for myself and I thought I would share.

It adapts ranger in neovim. It is very cool to have so much control, plus the previews.