vim-slash VS vim-projectionist

I changed most of the plugins I used for the mini versions, they are simple and lightweight and have a very simple configuration pattern. Thank you so much u/echasnovski for your work and dedication. Taking this opportunity, I would like to make a suggestion, a mini version of vim-slash, that automatically clears search highlight when cursor is moved in insert mode.

I just switched to using packer and recently added the plugin junegunn/vim-slash. I like the "auto clear highlight" but don't like some of the key bindings declared in the plugin. The plugin seems to be "done" so I can just fork it but I'd like to know if there's a solution for any plugin so I can easily keep my plugins up to date without having to manually merge.

romainl seems to recommend https://github.com/junegunn/vim-slash as a more complete alternative. Use whatever makes you happy.

There's also vim-slash

Obviously use / and * where possible. https://github.com/junegunn/vim-slash makes this more bearable.

You can use "*" for this if you have either https://github.com/haya14busa/vim-asterisk Or https://github.com/junegunn/vim-slash

https://github.com/junegunn/vim-slash This is useful as heck :D

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.