vscode-codicons
nvim-treesitter
vscode-codicons | nvim-treesitter | |
---|---|---|
9 | 300 | |
808 | 9,537 | |
1.6% | 3.3% | |
8.2 | 9.9 | |
21 days ago | 5 days ago | |
Handlebars | Scheme | |
Creative Commons Attribution 4.0 | 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.
vscode-codicons
-
How to Get a Unix-Like Terminal Environment in Windows and Visual Studio Code
What this does is create a custom terminal profile for all Windows environments. It tells VS Code to use cmd.exe to open C:\cmder\vendor\init.bat, which starts up Cmder. You can set the icon to any Codicon.
-
Some of the icons from Devicons not rendering properly in neovim despite I'm using nerd fonts
I experienced something similar. After some reasearch, I found out that the prebuilt fonts from https://www.nerdfonts.com/ are not patched with all the latest codicons set. I ultimately ended up patching a font myself using font-patcher. If you want, my patched version of Fira Code is in my nvim config. I just migrated to 0.9 over the weekend and all icons in neo-tree, dap-ui and telescope are displaying properly.
-
What sign icons do you use?
I prefer using codicons for all signs in Neovim.
-
Vim-dap-ui icons trouble
The default icons use codicons It's recommended to use this fork which fixes alignment issues for the terminal. If your terminal doesn't support font fallback and you need to have icons included in font you use you can patch it via Font Patcher. Simple step by step guide here.
-
nvim-tundra v0.2.0 - A punchy, dark theme for Neovim!
• Font is MonoLisa (unfortunately a paid font) • I use codicons with nvim-cmp to get the nice icons in auto-completion. • In my terminal (iTerm-2 on macOS, WezTerm on Windows) I’ve increased the height of the lines to 140% so text is spaced further apart vertically.
- Codicons shifted down a bit
-
How can I use codicons (like nerd fonts) in my diagnostic symbols?
Download and open in neovim https://github.com/microsoft/vscode-codicons/raw/main/dist/codicon.csv
-
Looks like the nvim-compe plugin is going to be deprecated, replaced by nvim-cmp (eventually)
Thanks! If you use the official VS Code codicons https://github.com/microsoft/vscode-codicons then this is the setup for you!
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?
nvim-cmp - A completion plugin for neovim coded in Lua.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
lspkind.nvim - vscode-like pictograms for neovim lsp completion items
nvim-lspconfig - Quickstart configs for Nvim LSP
neovim-codicons - The icon font for Visual Studio Code
vim-polyglot - A solid language pack for Vim.
cmp-nvim-lsp - nvim-cmp source for neovim builtin LSP client
vim-python-pep8-indent - A nicer Python indentation style for vim.
lspkind-nvim - vscode-like pictograms for neovim lsp completion items [Moved to: https://github.com/onsails/lspkind.nvim]
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
wezterm - A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
tree-sitter - An incremental parsing system for programming tools