-
### Describe the highlighting problem
The OneDarkPro colorscheme in VSCode highlights variables declared via `const` and `let` differently for JavaScript and TypeScript files. I wanted to have a si…
-
### Your OneDarkPro config
```lua
onedarkpro.setup({
-- Your onedarkpro config here
})
vim.cmd("colorscheme onedark")
```
### Error messages
_No response_
### Describe the bug
in w…
-
### Issue/Question/Enhancement
I noticed a few days ago that when I make changes to the filetype highlights in my onedarkpro config, the changes no longer apply immediately—when I quit `neovim` and…
-
### Enhancement
It would be nice if _onedarkpro.nvim_ can offer syntax highlights with the help of LSP.
Semantic token highlighting has been merged into the master branch of neovim https://github.…
-
The full error message is as follow:
```lua
packer.nvim: Error running config for heirline.nvim: ...m/lua/plugins/general/statusline/heir
line/statusline.lua:405: attempt to index a nil value
```
…
-
### Your OneDarkPro config
```lua
return {
'olimorris/onedarkpro.nvim',
config = function()
local onedarkpro = require('onedarkpro')
local utils = require('onedarkpro.lib.color')
…
-
There appears to be some kind of issue with sematic tokens when using vscode.nvim.
This is how code is highlighted when just using Treesitter:
![image](https://user-images.githubusercontent.com/3536…
-
VS Code settings:
```json
{
"workbench.colorTheme": "One Dark Pro",
"markdown-preview-github-styles.colorTheme": "light"
}
```
How it looks:
 lualine suppo…
-
### Issue/Question/Enhancement
Hello! Just a quick config issue I'm having. I don't know how to go about setting the `bg` of NvimTree to be a darker color...
I have a feeling it's through the `color…