vim-projectionist
vim-localvimrc
vim-projectionist | vim-localvimrc | |
---|---|---|
25 | 10 | |
1,033 | 475 | |
- | - | |
4.6 | 3.0 | |
about 2 months ago | about 1 month ago | |
Vim Script | Vim Script | |
- | GNU General Public License v3.0 only |
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-projectionist
-
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.
vim-localvimrc
-
Project & File navigation
A big part of 'project awareness' implies (to me at least!) that a project is organized in some meaningful way: test/view/model/service/domain files all relate to one another by their naming conventions and location in the project tree.When I start/join a project I look for documentation of the project's structure (or document it myself!). Then for vim:- use https://github.com/embear/vim-localvimrc - drop a .vimrc in the project so I can tweak vim to suit the project.
- Jinja and Django development
- exrc.nvim - Secure Project Local Config for Neovim
-
Project directory variable?
Something like Localvimrc?
-
Software engineers on big projects using vim, are you there?
Project-specific editor config: vim-localvimrc, vim-addon-local-vimrc
-
How do I override filetype for .yml files in the local project?
Is vim modeline a good way to do it? What do you think about that solution: https://github.com/embear/vim-localvimrc?
- Best way to have project specific settings?
-
AutoSource: Manage Vim configuration for local projects
This is pretty much the last one, but with available commands. One I find particularly useful is LocalVimRCCleanup. I'm not sure how common of a use-case this is, but AutoSource stores the hashes of each file you approved, and a common command I run while testing is rm ~/.autosource_hashdir/* :p
-
Running Tasks in Vim
Nice video. I have a similar approach for isolating project specific commands and configurations. I may borrow your idea for a project specific menu to run tasks. For a project dedicated vimrc I use embear/vim-localvimrc for a few years because it has auto discovery and auto change directory for a project, and require confirmation for loading the vimrc file.
What are some alternatives?
jumpwire.nvim - Jump easily between related files.
editorconfig-vim - EditorConfig plugin for Vim
denite.nvim - :dragon: Dark powered asynchronous unite all interfaces for Neovim/Vim8
exrc.vim - Local vimrc files
autojump - A cd command that learns - easily navigate directories from the command line
vim-dotenv - dotenv.vim: Basic support for .env and Procfile
vim-rails - rails.vim: Ruby on Rails power tools
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
bufexplorer - BufExplorer Plugin for Vim
vim-autosource - Manage Vim configuration for projects.
fzf.vim - fzf :heart: vim
ctrlp.vim - Fuzzy file, buffer, mru, tag, etc finder.