vim-rooter
coc.nvim
vim-rooter | coc.nvim | |
---|---|---|
24 | 322 | |
1,239 | 24,619 | |
0.9% | 0.5% | |
4.9 | 9.1 | |
4 months ago | 12 days ago | |
Vim Script | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
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-rooter
-
netrw made better
This or users may have monorepo style projects and vim-rooter to auto-set cwd to specific directories within the project based on certain file markers (e.g. makefile, package.json, ...etc), to accomplish something like :e dir1/file.go | make would run make and then :e dir2/file2.ts | make would run npm.
-
How to go up a directory while inside of telescope.nvim?
maybe you are already doing this and you want to access files outside the project directory but if not I use vim-rooter to set the root dir of the project automatically when I open vim
-
You don't need 'vim-rooter' (usually) or How to set up smart autochange of current directory
The airblade/vim-rooter plugin is an essential part of my Neovim workflow. It automatically changes current directory (:h current-directory) for every buffer to a more natural one (like to path of its Git repository). For me this has the following benefits:
-
Vim Issue with opened buffer file location
It depends where you open vim. If you are in home and open a file (even in sub directories) like nvim directory/file.txt, uour vim's current working directory (aka cwd) will be home. A way to make this automatic I think is the built in autocd (or something like that) and plugins like vim-rooter.
-
How to stop Telescope from changing the root directory after opening a file?
An alternative would be using a plugin like vim-rooter : https://github.com/airblade/vim-rooter
- NvimTree - how to get this behaviour?
-
How to properly cd, so plugins pick up project root?
I just use rooter and avoid thinking about it...
-
How to automatically cd to the git root of the current buffer?
There's vim-rooter, which is great.
- Whenever I'm looking for plugins these days [OC]
-
Whatโs the best start up screen written in Lua?
No, it doesn't change current directory. For that, use sessions or airblade/vim-rooter (or wait around couple of months for planned 'mini.root' :) ). And, of course, you can create custom items which will change current directory.
coc.nvim
-
How to Setup Vim for Kotlin Development
Neovim comes with a client. For Vim you will need to install one, such as CoC, LanguageClient-neovim, or vim-lsp.
-
Lite ๐ ApolloNvim Distro 2024
๐ With LSP in this installation, I use Coc for its simplicity without the need to intervene in the Coc configuration. LSP has been very useful in my Helix modal editor to configure Helixu.
-
I can't stand using VSCode so I wrote my own (it wasn't easy)
As well as its own plugins Vim/NeoVim can use VSCode's LSPs, DAPs and extensions either directly or via plugins like CoC[1] and Mason[2].
I would be surprised if emacs couldn't do the same.
1. https://github.com/neoclide/coc.nvim
-
Existing non-lua plugins examples
The most famous TypeScript one probably is coc.nvim
-
ready to use neovim for web development (frontend) - beginners
It is flatly the wrong mindset to think of vim as an IDE. vim is a code editor: get in, make change, get out. Consider vim koans, which are a fun little read. You can throw coc.nvim at Neovim, along with a few other bits to give you a Good Enough setup, but vim isn't and will never be an IDE.
-
Using CoC inlay hints
I just did a fresh reinstall of CoC, on a newer version of Neovim. I'm now seeing something I hadn't seen before, which CoC calls "inlay hints". They look like this:
-
C# lsp configuration with neovim CoC
I'm currently on an old setup (using coc and polyglot) and nvim v0.6.1. I'll be updating to a more modern setup within next year, using the native lsp and building nvim more frequently. But that's not today.
-
Does anyone know some good altermatives for these Vim plugins on Emacs?
coc.nvim
-
LazyVim
There are some plugins which have the best documentations I have ever seen, but you need to read it from the Vim.
Example of coc.nvim: https://github.com/neoclide/coc.nvim/blob/master/doc/coc.txt
-
Resources on learning bash scripting
Actually you can with coc.nvim & coc-sh. So long as shellcheck is also installed and in PATH, it'll integrate with coc/vim just fine.
What are some alternatives?
project.nvim - The superior project management solution for neovim.
mason.nvim - Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters.
vim-startify - :link: The fancy start screen for Vim.
YouCompleteMe - A code-completion engine for Vim
nvim-bqf - Better quickfix window in Neovim, polish old quickfix window.
LazyVim - Neovim config for the lazy
vim-grepper - :space_invader: Helps you win at grep.
nvim-cmp - A completion plugin for neovim coded in Lua.
replacer.nvim - A powerful refactoring tool for nvim.
nvim-treesitter - Nvim Treesitter configurations and abstraction layer
nvim-spectre - Find the enemy and replace them with dark power.
vim-lsp - async language server protocol plugin for vim and neovim