dotfiles VS vim-projectionist

I have never used lsp-zero nor mason. I crafted my own LSP setup from back in the Neovim 0.5 days, see config here if interested.

Very simple, as noted here

My Diagnostic config: https://github.com/bluz71/dotfiles/blob/master/nvim/after/plugin/diagnostic.lua

My Neovim dotfiles.

init.lua and nvim directory

Most of mine is in Vimscript except for any modern Neovim plugin, I configure all of those in Lua. You can so I sprinkle Lua lightly within my configuration.

[Tip 3] Do not use the vim-rails plugin, it really slows down startup A LOT. I have switched over to Tim Pope's other project navigation plugin projectionist which can be configured to provide most of the functionality of vim-rails (but not all). For those interested here are my projectionist mappings. The stuff I miss out on, such as opening view files under the cursor just via :Eview, I can live without.

You can look around my dotfiles to get a feel for this hybrid Neovim / Vim compatibility mode.

This is what it looks like for me and this is my indent-blankline configuration, the most important of which is this:

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.