.dotfiles
nvim-treesitter
.dotfiles | nvim-treesitter | |
---|---|---|
12 | 300 | |
114 | 9,537 | |
- | 3.3% | |
7.5 | 9.9 | |
28 days ago | 1 day ago | |
Lua | Scheme | |
- | 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.
.dotfiles
-
Implement the handler for LSP textDocument/onTypeFormatting ?
I also did a simple script to test it out a while ago. As you might have realized, this functionality needs to listen for a few triggering characters depending on the language server, kinda like autocomplete implemented by nvim-cmp. So, I guess, until they merge the autocomplete functionality to core, this won't be added. You could, in the meanwhile, create a nvim-cmp plugin and simplify quite a bit what you already have done.
-
[Help] Convert LaTeX UltiSnips Snippets to LuaSnip
I have some here https://github.com/tiagovla/.dotfiles/tree/master/neovim/.config/nvim/lua/plugins/config/luasnip/snips . You can create contextual snippets with treesitter. Autosnipet is also an option.
-
LSP codelens and inlayhints
I got this to work with python inlayhints https://github.com/tiagovla/.dotfiles/tree/master/neovim/.config/nvim/lua/lsp/inlay_hints and this should enable those `require("lsp.inlay_hints").setup_autocmd()`.
-
Taking notes in class with LaTeX
I'm quite happy with only texlab + nvim-cmp + luasnips. That's it. I have some snippets here https://github.com/tiagovla/.dotfiles/tree/master/neovim/.config/nvim/lua/plugins/config/luasnip/snips for latex if you need a place to start (just require the files).
-
File Structure for Adjusting Plugin Options
I think everyone does this in their own way. I like to separate user settings and plugins in different folders inside the lua folder. And every plugin has its own config (setup, mappings, ...), so I can enable/disable them in a single place. My dots look like this.
-
How can I load a user dictionary into ltex-ls?
Btw, I coded this https://github.com/tiagovla/.dotfiles/blob/0f664e30def1e460dd04fc8276f0d12f1ee2e88b/neovim/.config/nvim/lua/plugins/config/lsp/custom_servers/ltex.lua
-
I'm looking for a comfortable neovim based environment for Python and IPython
Oh, for sure! Here you go https://github.com/tiagovla/.dotfiles
-
Help with vimrc
I have it in place https://github.com/tiagovla/dotfiles/blob/master/nvim/lua/plug-config/lsp/settings.lua
-
New TokyoDark Theme
Do you the have the colors matched here? https://github.com/tiagovla/dotfiles/blob/master/.tmux.conf#L37-L43
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?
lspsaga.nvim - improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim]
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
gruvbox.nvim - Lua port of the most famous vim colorscheme
nvim-lspconfig - Quickstart configs for Nvim LSP
jupyter-vim - Make Vim talk to Jupyter kernels
vim-polyglot - A solid language pack for Vim.
gitsigns.nvim - Git integration for buffers
vim-python-pep8-indent - A nicer Python indentation style for vim.
nvim-type-fmt - LSP handler of textDocument/onTypeFormatting for nvim.
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
nvim-compe - Auto completion Lua plugin for nvim
tree-sitter - An incremental parsing system for programming tools