a.vim
Alternate Files quickly (.c --> .h etc) (by vim-scripts)
vim-projectionist
projectionist.vim: Granular project configuration (by tpope)
| a.vim | vim-projectionist | |
|---|---|---|
| 4 | 25 | |
| 307 | 1,033 | |
| - | - | |
| 0.0 | 4.6 | |
| over 1 year ago | about 2 months ago | |
| VimL | Vim Script | |
| - | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
a.vim
Posts with mentions or reviews of a.vim.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-04-24.
-
other.nvim - open alternative files for the current buffer.
The plugin is inspired by vim-projectionist and https://github.com/vim-scripts/a.vim
-
nvim-quick-switcher: Navigate related files quickly (My first plugin)
Many years ago I used a plugin with the simple name "a.vim". https://github.com/vim-scripts/a.vim
-
How to update vim packages?
I have everything in my .dotfiles git bare repo. For vim plugins, it's something like this in .gitmodules. I'm pretty sure most native plugin manager users do it like this, if they have internet access. The version is locked and you have to manually update the commit hash. [submodule ".vim/pack/git-plugins/start/a.vim"] path = .vim/pack/git-plugins/start/a.vim url = https://github.com/vim-scripts/a.vim
-
Can you create a header and class file within vim? Can't find any commands or if there's a plugin [C++]
There’s also this: https://github.com/vim-scripts/a.vim. Not exactly the same use-case, but extremely handy nonetheless.
vim-projectionist
Posts with mentions or reviews of vim-projectionist.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-18.
-
What plugins do you use to manage work across multiple files?
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.
-
A few words on Ruby's type annotations state
> 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
-
What's the coolest thing you've done with Neovim?
One of the originals I guess must be tim pope's https://github.com/tpope/vim-projectionist
- Could use some advice for managing projects in a way that fits my mental model and codebase. Monolithic codebase with project files spread around different working directories. Or just help me change my mental model.
-
Project & File navigation
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!)
-
New Plugin: telescope-alternate
I love Tpope’s https://github.com/tpope/vim-projectionist but this one seems like a great replacement 😎
-
JVM language users- how do you write your test files?
Tim Pope's excellent Projectionist plug-in has an alternate file feature, which makes it very easy to switch between test and implementation files.
-
other.nvim - open alternative files for the current buffer.
The plugin is inspired by vim-projectionist and https://github.com/vim-scripts/a.vim
-
vim-projectionist isn't autoloading in 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
-
Auto-open unit test file
You need https://github.com/tpope/vim-projectionist. Gotta have a file structure for unit tests though.