vim-autosource
Manage Vim configuration for projects. (by jenterkin)
vim-projectionist
projectionist.vim: Granular project configuration (by tpope)
| vim-autosource | vim-projectionist | |
|---|---|---|
| 8 | 25 | |
| 30 | 1,033 | |
| - | - | |
| 0.0 | 4.6 | |
| almost 2 years ago | about 2 months ago | |
| Vim Script | Vim Script | |
| MIT License | - |
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.
vim-autosource
Posts with mentions or reviews of vim-autosource.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-16.
-
How to properly use a conda environment inside neovim?
I use https://github.com/jenterkin/vim-autosource
- A configurable neovim flake/module
- Resources on project specific vim setup
-
HOW DO I MAKE A PROJECT SYSTEM
:set exrc and and create .exrc file in your project directory with your project settings, or use a plugin like https://github.com/ii14/exrc.vim or https://github.com/jenterkin/vim-autosource
-
AutoSource: Manage Vim configuration for local projects
Oh, absolutely. I thought about it over dinner and couldn't think of why I wouldn't add that soooo here ya go.
jenterkin/vim-autosource
- Feedback on a small vim plugin
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.
What are some alternatives?
When comparing vim-autosource and vim-projectionist you can also consider the following projects:
exrc.vim - Local vimrc files
jumpwire.nvim - Jump easily between related files.
nvim-projectconfig - neovim projectconfig
denite.nvim - :dragon: Dark powered asynchronous unite all interfaces for Neovim/Vim8
vim-localvimrc - Search local vimrc files (".lvimrc") in the tree (root dir up to current dir) and load them.
autojump - A cd command that learns - easily navigate directories from the command line
direnv - unclutter your .profile
vim-rails - rails.vim: Ruby on Rails power tools
neovim-flake - Nix flake for neovim with configuration
bufexplorer - BufExplorer Plugin for Vim
vim-startify - :link: The fancy start screen for Vim.
fzf.vim - fzf :heart: vim
vim-autosource vs exrc.vim
vim-projectionist vs jumpwire.nvim
vim-autosource vs nvim-projectconfig
vim-projectionist vs denite.nvim
vim-autosource vs vim-localvimrc
vim-projectionist vs autojump
vim-autosource vs direnv
vim-projectionist vs vim-rails
vim-autosource vs neovim-flake
vim-projectionist vs bufexplorer
vim-autosource vs vim-startify
vim-projectionist vs fzf.vim