vim-gitgutter
nvim-treesitter
Our great sponsors
vim-gitgutter | nvim-treesitter | |
---|---|---|
32 | 300 | |
8,276 | 9,487 | |
- | 5.4% | |
7.7 | 9.9 | |
3 months ago | 2 days ago | |
Vim Script | Scheme | |
MIT License | Apache License 2.0 |
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-gitgutter
-
I use the default file browser in vim (netrw). I know there are plugins that a lot of people like. Should I switch?
I personally use nerdtree. Add nerdtree-git-plugin too, that's nice when looking at your project (for files, use vim-gitgutter).
-
How to configure vim like an IDE
vim-gitgutter
-
Margin indicator for Neovim
That said, Neovim can still run most Vimscript plugins just fine, so you can still use https://github.com/chrisbra/changesPlugin (and https://github.com/airblade/vim-gitgutter and https://github.com/mhinz/vim-signify/, which are mentioned in the README) if you want.
-
:DiffOrig changes reflected in sign column
vim-signify or git gutter can do this for files managed by git.
- Is there a simple way to see if a certain line has unsaved changes?
-
What "new-to-you" tool did you recently start using that just changed your workflow for the better?
https://github.com/tpope/vim-fugitive https://github.com/airblade/vim-gitgutter Since your already on neovim these plugins are excellent for git integration within vim! You may just prefer lazygit but having a tight integration in editor is definitely really nice for my personal workflow. Your approach is more unix-y where you have a tool for each job though!
- Neovim - Workflow para Java, C# e JS/TypeScript (Atualização com Neovim 0.8 e LSP)
-
Neovim config from scratch (Part I)
Git gutter Git status signs in the gutter (leftmost column)
- What plugins do yall use for Git
-
Are there plugins for Neovim that don't exist, that should exist, in your opinion?
vim-gitgutter supports staging/undoing hunks and a hunk text object. I find it convenient for this exact workflow.
nvim-treesitter
-
JetBrains' unremovable AI assistant meets irresistible outcry
I suggest looking for blog posts about this, you're gunnuh wanna pick out a plugin manager and stuff. It's kind of like a package manager for neovim. You can install everything manually but usually you manually install a plugin manager and it gives you commands to manage the rest of your plugins.
These two plugins are the bare minimum in my view.
https://github.com/nvim-treesitter/nvim-treesitter
Treesitter gives you much better syntax highlighting based on a parser for a given language.
https://github.com/neovim/nvim-lspconfig
This plugin helps you connect to a given language LSP quickly with sensible defaults. You more or less pick your language from here and copy paste a snippet, and then install the relevant LSP:
https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser...
For Python you'll want pylsp. For JavaScript it will depend on what frontend framework you're using, I probably can't help you there.
pylsp itself takes some plugins and you'll probably want them. https://github.com/python-lsp/python-lsp-server
Best of luck! Happy hacking.
-
Help needed with Treesitter sql injection
It was changed in https://github.com/nvim-treesitter/nvim-treesitter/commit/78b54eb
-
Do I need NeoVIM?
https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.
- Problem with highlighting when attempting to create own treesitter parser
-
neorg problem, all other plugins deactivate when added to init.lua
vim.opt.rtp:prepend(lazypath) require('lazy').setup({ { "nvim-neorg/neorg", build = ":Neorg sync-parsers", opts = { load = { ["core.defaults"] = {}, -- Loads default behaviour ["core.concealer"] = {}, -- Adds pretty icons to your documents ["core.dirman"] = { -- Manages Neorg workspaces config = { workspaces = { notes = "~/notes", }, defaultworkspace = "notes", }, }, }, }, dependencies = { { "nvim-lua/plenary.nvim", }, { -- YOU ALMOST CERTAINLY WANT A MORE ROBUST nvim-treesitter SETUP -- see https://github.com/nvim-treesitter/nvim-treesitter "nvim-treesitter/nvim-treesitter", opts = { auto_install = true, highlight = { enable = true, additional_vim_regex_highlighting = false, }, }, config = function(,opts) require('nvim-treesitter.configs').setup(opts) end }, { "folke/tokyonight.nvim", config=function(,) vim.cmd.colorscheme "tokyonight-storm" end,}, }, }, }) require 'plugins' ```
-
Getting Treesitter to work for Windows 10
Change the compiler to use 'llvm' and install visual studio build tools command line stuff - at least that is what worked for me without problems. If you are using c++ then I would assume you have visual studio installed already. If you need more info follow the treesitter windows support
-
Just come back up out of the rabbit hole - TS unsets syntax variable by design!
After a lot of time spent yesterday I took a fresh look today and then thought to myself - what if this is what TS does by design? A few clicks later and I found this https://github.com/nvim-treesitter/nvim-treesitter/issues/1327
- What is this color scheme
-
nvim-treesitter erroring on Windows 11 Pro
I've followed the official guide for nvim-treesitter support on Windows, but I'm having problems making it work. I keep getting a compilation error for any parser I try to install using TSInstall. If instead I use TSInstallSync I don't get errors but the parser is not correctly installed. My setup uses lazyvim and I installed LLVM using winget to have a C compiler.
-
Neovim can't find C compiler
I have read that gcc in windows doesn't always provide the necessary support for treesitter. I have seen ppl prefer clang over gcc in Windows. Please see also Windows support in treesitter's repo. Unfortunately I cannot help further as I don't use Windows for coding, but hope you can deduce something to solve your problem from the above link (if you haven't already read through it).
What are some alternatives?
vim-fugitive - fugitive.vim: A Git wrapper so awesome, it should be illegal
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
nvim-tree.lua - A file explorer tree for neovim written in lua
nvim-lspconfig - Quickstart configs for Nvim LSP
gitsigns.nvim - Git integration for buffers
vim-polyglot - A solid language pack for Vim.
vim-signify - :heavy_plus_sign: Show a diff using Vim its sign column.
vim-python-pep8-indent - A nicer Python indentation style for vim.
lualine.nvim - A blazing fast and easy to configure neovim statusline plugin written in pure lua.
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
tree-sitter - An incremental parsing system for programming tools