ctags | fzf.vim | |
---|---|---|
33 | 157 | |
6,292 | 9,401 | |
1.9% | - | |
9.7 | 6.6 | |
9 days ago | 6 days ago | |
C | Vim Script | |
GNU General Public License v3.0 only | 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.
ctags
- If you owned a nvidia tesla a100, what would you do with it?
-
NeoVim & Rust
I also recommend you https://github.com/preservim/tagbar with https://ctags.io/ installed , it will map definitions (functions, enum, struct etc..) to tags and tagbar plugin allows you to open a split window with the mapped list and navigate through your file, it also enabled more advanced features for quick navigation .
-
How do you figure out which #include a function/variable came from?
grep, Ctags, Cscope, LSP
-
Vim plugin like vscode "go to definition" function
Vim has the tag feature built-in, which allows it to jump to the tags that were found by a tool like universal ctags using :h CTRL-]. See :help tags for more information on this. Fun fact: this is the approach that Vim uses when you use :help!
-
Neovim config from scratch (Part II)
Requirements: You need to have a CTags implementation like universal-ctags installed on your system (on every system where you use vim).
-
How to check the memory usage of my plugins?
Install https://github.com/universal-ctags/ctags
-
Project reading tools
If you are heavy Vim user, you do not need anything else. For just quick browsing, simply use ctags, make sure to use universal ctags (https://ctags.io) not exuberant ctags which are no longer well maintained. Go works out of box.
-
Help me set up vim for linting and a file tree please and some other stuff
Other (built-in) tools for file navigation in Vim include: :h :ls and :h :buffer to navigate in your buffer list (i.e. the files you have loaded); everything listed in [https://vimways.org/2018/death-by-a-thousand-files/](romainl's "Death by a Thousand Files" articles in vimways); using tags by installing universal-ctags to generate the tags then using any of the commands in :h tag to navigate them; setting global marks to files you use often with m[UPPERCASE LETTER] and jumping to them with `[UPPERCASE LETTER]; :h :vimgrep…
-
Ctags and referencing static functions, is it possible?
I have good news for you. Universal Ctags, an Exuberant Ctags fork and essentially its replacement, has fixed this already:
-
Searching files or words using fuzzy finders
Vim has built-in functionality that works pretty similar to what you want. If you have a tags file (for example, using universal ctags), you can hit Ctrl-] (:h Ctrl-]) to jump to the declaration of any function under your cursor. Or, if you don't have a tags file, you can use gd (:h gd) to jump to a local declaration within the open file.
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?
lsp-mode - Emacs client/library for the Language Server Protocol
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
vscode-intelephense - PHP intellisense for Visual Studio Code
ctrlp.vim - Fuzzy file, buffer, mru, tag, etc finder.
lsp - Language Server Protocol (LSP) plugin for Vim9
nerdtree - A tree explorer plugin for vim.
nvim-lspconfig - Quickstart configs for Nvim LSP
fzf-lua - Improved fzf.vim written in lua
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
harpoon
vim-gutentags - A Vim plugin that manages your tag files
nvim-tree.lua - A file explorer tree for neovim written in lua