vim-projectionist
fzf.vim
vim-projectionist | fzf.vim | |
---|---|---|
25 | 157 | |
1,033 | 9,418 | |
- | - | |
4.6 | 6.6 | |
about 2 months ago | 6 days ago | |
Vim Script | Vim Script | |
- | MIT License |
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.
fzf.vim
-
What are some plugins that you can't live without?
Fuzzy Finder: fzf.vim (for its speed) along with telescope.nvim (for its ecosystem)
-
Ripgrep is faster than {grep, ag, Git grep, ucg, pt, sift}
https://github.com/junegunn/fzf.vim
And added my keyboard shortcuts.
-
A Practical Guide to fzf: Vim Integration
There are two plugins allowing us to use fzf in Vim: the native fzf plugin directly installed with fzf, and fzf.vim. The second plugin is built on the first one.
-
LazyVim
You might be interested in installing the fzf-vim plugin [0]. It has a user-defined command :Maps which can be used to search through all keybindings (you can also do this with just :nmap in vim, but the fzf interface is much nicer). It also provides :Commands. This behaves remarkably like VSCode's command palette.
[0] https://github.com/junegunn/fzf.vim
-
Manual page in vim with fuzzy search with preview, documentation with cherry on top.
You'll also need https://github.com/junegunn/fzf.vim (which is imo the only vim plugin that's a must).
-
I use the default file browser in vim (netrw). I know there are plugins that a lot of people like. Should I switch?
I do all my file operations from the command line. But to open and search files I use fzf
-
How to use popup and fuzzy in vim9
Regarding plugins , I am using https://github.com/Donaldttt/fuzzyy because it works in windows, unlike https://github.com/junegunn/fzf.vim
-
Alternative to harpoon for vim to quickly navigate few files/buffers
There's a :Buffers command in fzf.vim that I use extensively. It opens a fuzzy-find window with all open buffers in a MRU list.
-
fzfx.vim: E(x)tended fzf commands missing in fzf.vim
Thanks to fzf.vim and fzf-lua, everything I learned and copied is from them.
-
jfind: over 130x faster than telescope + telescope-fzf-native
they're likely referring to fzf.vim, the vimscript plugin from the original fzf author that wraps around fzf. there's also fzf-lua nowadays.
What are some alternatives?
jumpwire.nvim - Jump easily between related files.
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
denite.nvim - :dragon: Dark powered asynchronous unite all interfaces for Neovim/Vim8
ctrlp.vim - Fuzzy file, buffer, mru, tag, etc finder.
autojump - A cd command that learns - easily navigate directories from the command line
nerdtree - A tree explorer plugin for vim.
vim-rails - rails.vim: Ruby on Rails power tools
fzf-lua - Improved fzf.vim written in lua
bufexplorer - BufExplorer Plugin for Vim
harpoon
vim-grepper - :space_invader: Helps you win at grep.
nvim-tree.lua - A file explorer tree for neovim written in lua