nvim-web-devicons VS nvim-treesitter

I know you moved on dotfiles, which is good, but you will probably want to install https://github.com/nvim-tree/nvim-web-devicons to get those icons for other plugins

This is already done I think, unless more fixes are needed https://github.com/nvim-tree/nvim-web-devicons/pull/264

Motivation: I have been using Emacs for years but I never really sit down and wrote any serious elisp code myself. This time things changed because I saw the nvim-web-devicons. I like trying various kinds of editors, and then I found this devicons from vim editor so good. I really like it especially because it works in the terminal. People always say Emacs is best within GUI but there are times when you have to edit something in a terminal and maybe some like me just like terminal aesthetics. I mean I really like this devicons theme from vim but I never really liked vim keybindings. I want it to be part of Emacs so bad so I finally decided to learn some elisp and make it happen.

Did you install this plugin?

Did you install https://github.com/nvim-tree/nvim-web-devicons ?

nvim-web-devicons is a plugin that maps filetypes to icons in a patched font and colors for those icons. It has default settings for both the icons and colors for many common filetypes, but they can be customized and you can add support for your own filetypes.

It uses plugins called renderer to change how the file tree is renderer and it has two plugins for render icons in the tree that support lambdalisue/nerdfont.vim and ryanoasis/vim-devicons, but it lacked support for nvim-web-devicons.

I'm configuring neovim 0.8 on windows. I've installed nvim-tree plugin with its icons nvim-web-devicons. After the installation I cannot see properly the icons in the tree. This is the screenshot with the tree and the configuration part about those plugins:

The "look" you're looking for is given by a bunch of plugins: - OneDark.nvim as colorscheme - TS Rainbow for rainbow brackets - BarBar for bufferline - Nvim Devicons and NerdFonts to view file icons - NvimTree as a file manager - Indent Blankline to show indentation guides - CompetiTest with vertical split UI - Feline as statusline plugin. In the screenshot feline is configured with a custom theme. As you can see statusline is different for CompetiTest buffers: a different statusline can be configured for every different filetype using conditional_config.

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.

It was changed in https://github.com/nvim-treesitter/nvim-treesitter/commit/78b54eb

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.

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' ```

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

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

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.

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).