tokyo-night-vscode-theme
nvim-treesitter
tokyo-night-vscode-theme | nvim-treesitter | |
---|---|---|
11 | 300 | |
1,461 | 9,537 | |
- | 3.3% | |
6.5 | 9.9 | |
about 2 months ago | 2 days ago | |
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.
tokyo-night-vscode-theme
- Can anyone tell me what theme this is?
- Looking for Tokyo Night Light theme
-
Solarized
Has anyone done a cross-app configuration tool for color themes yet ? It seems most themes just reimplement everything. For example, I like tokyonight, but it seems everyone needs to port it to their favorite tool, just like solarized did:
https://github.com/enkia/tokyo-night-vscode-theme#other-port...
Even the open source and professional theme Dracula seem to rely on manual porting:
https://github.com/dracula/dracula-theme
-
199 packages
Tokyo Night for kitty, but it's also available for many other applications
-
✨🏮 Tokyo Night by Niivu🌙✨
Based on: Tokyo Night by Enkia
-
Tokyo Night on Windows 11
palette
-
Tokyo Night Theme for All Jetbrains IDE
Original VSCode theme: https://github.com/enkia/tokyo-night-vscode-theme
-
Iosevka Night [HD/STD/16:9]
Tokyo Night colourscheme
-
My first mock up designs for my company's website homepage
So the spot for the images is supposed to be slideshow of images. It would showcase our products and what they can do. The colors we use are based on the "Tokyo Night" theme by enkia. This color scheme is the one we use in our biggest product, ExpidusOS, so it makes sense our website is themed after it. And yes, I do the design and development.
-
[Media] Struct Update Syntax in Rust
Tokyo Night Storm. If you scroll to the bottom there are some extra versions, like the vim one.
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?
tokyonight.nvim - 🏙 A clean, dark Neovim theme written in Lua, with support for lsp, treesitter and lots of plugins. Includes additional themes for Kitty, Alacritty, iTerm and Fish.
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
tokyonight-vim - [ARCHIVED : Lack of time to maintain] A clean, dark vim colorscheme that celebrates the lights of downtown Tokyo at night, based on a VSCode theme by @enkia with the same name
nvim-lspconfig - Quickstart configs for Nvim LSP
dashboard-nvim - vim dashboard
vim-polyglot - A solid language pack for Vim.
lspsaga.nvim - improve neovim lsp experience [Moved to: https://github.com/nvimdev/lspsaga.nvim]
vim-python-pep8-indent - A nicer Python indentation style for vim.
neovim - Vim-fork focused on extensibility and usability
packer.nvim - A use-package inspired plugin manager for Neovim. Uses native packages, supports Luarocks dependencies, written in Lua, allows for expressive config
vim-airline - lean & mean status/tabline for vim that's light as air
tree-sitter - An incremental parsing system for programming tools