ranger.vim VS vim-projectionist

This plugin is unique from the other alternatives such as ranger.vim and rnvimr in that my plugin has no dependencies besides ‘ranger’ and written in 100% lua.

ranger.vim that integrates the file explorer ranger into vim. (Superior to NERDTree IMHO)

ranger, I got so used to using it and invested in learning many of its features that I can navigate around quite fast. I'm using francoiscabrol/ranger.vim but I have been meaning to check out kevinhwang91/rnvimr. I'm even using a fork which supports coloured icons.

I Installed Ranger plugin (https://github.com/francoiscabrol/ranger.vim) for File exploring and I experienced a very stupid problem. When I navigate and select a Typescript file to open, instead of being opened as text vim Nvim it opens as executable. At first it was VLC media player and now when I changed to iTerm it just reopens it in a separate window. How can I fix it ?

If I really want to see the tree (once a year), I use ranger via this plugin

I've been very happy with https://github.com/francoiscabrol/ranger.vim as well

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.