DeathVim
nvim-treesitter
DeathVim | nvim-treesitter | |
---|---|---|
22 | 300 | |
110 | 9,588 | |
- | 3.8% | |
7.9 | 9.9 | |
over 1 year ago | 6 days ago | |
Lua | Scheme | |
GNU General Public License v3.0 only | 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.
DeathVim
-
I'm extremely happy with DeathVim's look and performance. So, I thought I'd share.
I opened the issue a few weeks ago https://github.com/SingularisArt/DeathVim/issues/10
-
The first release of DeathVim
If you want to see my future plans for this project, you can view here
-
Creating a logo for my community
My community is based on a program that I and a few others built. It's a text editor called DeathVim. Here's the link to my community. The point of this community is to make it easier for people to start coding so they don't have to waste any time setting everything up themselves. They can actually just learn to program, which is something I was I had when I first started about 2 1/2 years ago.
-
Trying to create a LunarVim like IDE setup, called DeathVim
As for lualine, I do use it. You can view my configuration for that here
I use winbar
-
My first BSPWM CONFIGURATION (I don't know if I should post here or not, but whatever)
Website (This has some information on my dotfiles and neovim config)
-
My updated neovim setup Sorry. too lazy to get more pics. :(
Links: NeoVim Config here (Note: I have to update the images)
-
Structuring my Python Programs
If you want, you can look at my NeoVim configuration here. Hopefully, you will end up going back to NeoVim!
-
Debugging in NeoVim
Dap Configuration folder
-
My updated neovim config (inspired from NVChad, Wincent, and Lunar Vim)
My NeoVim Config: here
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?
DAPInstall.nvim - 🦆 A NeoVim plugin for managing several debuggers for Nvim-dap
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
nvim-lspconfig - Quickstart configs for Nvim LSP
nightfox.nvim - 🦊A highly customizable theme for vim and neovim with support for lsp, treesitter and a variety of plugins.
vim-polyglot - A solid language pack for Vim.
nvim-gps - Simple statusline component that shows what scope you are working inside
vim-python-pep8-indent - A nicer Python indentation style for vim.
nvim-dap-ui - A UI for nvim-dap
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
vim-ultest - The ultimate testing plugin for (Neo)Vim
tree-sitter - An incremental parsing system for programming tools