[{"result":{"data":[{"id":"990a291c-1359-4829-afaa-47681ff2783f","title":"feat!: updated python treesitter queries","text":"feat!: updated python treesitter queries","type":"breaking-change","createdAt":"2023-11-13T02:18:55.081Z","breakingChange":{"id":89,"postId":"990a291c-1359-4829-afaa-47681ff2783f","pluginId":215,"externalUrl":"https://github.com/olimorris/onedarkpro.nvim/commit/f3a7349156453500f1c053a1f8034a3975b1d793","sha":"f3a7349156453500f1c053a1f8034a3975b1d793","plugin":{"id":215,"owner":"olimorris","name":"onedarkpro.nvim","type":"github","source":"awesome-neovim","category":"colorscheme","link":"https://github.com/olimorris/onedarkpro.nvim","shortDescription":"🎨 Atom's iconic One Dark theme, for Neovim. Fully customisable, with Treesitter, LSP semantic token support and a light variant","createdAt":"2023-03-22T19:35:21.592Z","readme":"\n\n

\n $\"OneDarkPro.nvim\"$ \n

\n\n

OneDarkPro.nvim

\n\n

\n\n\n\n\n

\n\n

\n Atom's iconic One Dark theme for Neovim.
\n Fully customisable, with Treesitter, LSP semantic tokens and support for many common plugins.

\n Based on the amazing One Dark Pro theme for Visual Studio Code.\n

\n\n## :icecream: Themes\n\n> **Note**: All bolds and italics in the screenshots below are [completely customisable](#configuring-styles)\n\n

Onedark $\"onedark\"$

Onelight $\"onelight\"$

Onedark Vivid $\"onedark$

Onedark Dark $\"onedark$

\n\n\n\n## :sparkles: Features\n\n- :envelope_with_arrow: Automatic caching for faster load times\n- :evergreen_tree: Full [Treesitter](https://github.com/nvim-treesitter/nvim-treesitter) support and bespoke queries\n- :tickets: Support for LSP semantic tokens\n- :electric_plug: Support for many [popular plugins](#electric_plug-supported-plugins)\n- :flashlight: Filetype highlighting to allow for greater customisation across different languages\n- :memo: Override everything - styles, colors, tokens, highlight groups and filetype groups\n- :paintbrush: Create custom highlight groups and even highlight groups by filetypes\n\n## :zap: Requirements\n\n- Neovim 0.9.0+\n- `termguicolors` enabled for true color support\n- `treesitter` for full syntax highlighting\n- For semantic tokens, an LSP server that supports them\n\n## :package: Installation and usage\n\nInstall with your package manager of choice:\n\n```lua\n-- Lazy\n{\n \"olimorris/onedarkpro.nvim\",\n priority = 1000 -- Ensure it loads first\n}\n\n-- somewhere in your config:\nvim.cmd(\"colorscheme onedark\")\n```\n\n```lua\n-- Packer\nuse \"olimorris/onedarkpro.nvim\"\n\n-- somewhere in your config:\nvim.cmd(\"colorscheme onedark\")\n```\n\n```vim\n\" Vim-Plug\nPlug \"olimorris/onedarkpro.nvim\"\n\n\" somewhere in your config:\ncolorscheme onedark\n```\n\n## :rocket: Commands\n\nThe colorscheme comes with some useful commands:\n\n- `:OnedarkproCache` force generate new cache files for the themes (you won't often need this)\n- `:OnedarkproClean` removes existing cache files for the themes\n- `:OnedarkproColors` output all of the current themes colors to a scratch buffer\n\nThe theme comes with the ability to export colors to _Alacritty_, _Kitty_, _Foot_, _Wezterm_, _Rio_ and _Windows Terminal_ using the following commands:\n\n- `:OnedarkproExportToAlacritty`\n- `:OnedarkproExportToFoot`\n- `:OnedarkproExportToKitty`\n- `:OnedarkproExportToWezterm`\n- `:OnedarkproExportToWindowsTerminal`\n- `:OnedarkproExportToRio`\n\nThe templates for these themes can be found in the [extra](https://github.com/olimorris/onedarkpro.nvim/tree/main/lua/onedarkpro/extra) folder.\n\n## :wrench: Configuration\n\n### Default configuration\n\n> **Note**: You only need to the call the `setup` function if you wish to change any of the defaults.\n\n

Click to see the default configuration

\n\n```lua\nrequire(\"onedarkpro\").setup({\n colors = {}, -- Override default colors or create your own\n highlights = {}, -- Override default highlight groups or create your own\n styles = { -- For example, to apply bold and italic, use \"bold,italic\"\n types = \"NONE\", -- Style that is applied to types\n methods = \"NONE\", -- Style that is applied to methods\n numbers = \"NONE\", -- Style that is applied to numbers\n strings = \"NONE\", -- Style that is applied to strings\n comments = \"NONE\", -- Style that is applied to comments\n keywords = \"NONE\", -- Style that is applied to keywords\n constants = \"NONE\", -- Style that is applied to constants\n functions = \"NONE\", -- Style that is applied to functions\n operators = \"NONE\", -- Style that is applied to operators\n variables = \"NONE\", -- Style that is applied to variables\n parameters = \"NONE\", -- Style that is applied to parameters\n conditionals = \"NONE\", -- Style that is applied to conditionals\n virtual_text = \"NONE\", -- Style that is applied to virtual text\n },\n filetypes = { -- Override which filetype highlight groups are loaded\n comment = true,\n go = true,\n html = true,\n java = true,\n javascript = true,\n json = true,\n lua = true,\n markdown = true,\n php = true,\n python = true,\n ruby = true,\n rust = true,\n scss = true,\n toml = true,\n typescript = true,\n typescriptreact = true,\n vue = true,\n xml = true,\n yaml = true,\n },\n plugins = { -- Override which plugin highlight groups are loaded\n aerial = true,\n barbar = true,\n copilot = true,\n dashboard = true,\n flash_nvim = true,\n gitsigns = true,\n hop = true,\n indentline = true,\n leap = true,\n lsp_saga = true,\n lsp_semantic_tokens = true,\n marks = true,\n mini_indentscope = true,\n neotest = true,\n neo_tree = true,\n nvim_cmp = true,\n nvim_bqf = true,\n nvim_dap = true,\n nvim_dap_ui = true,\n nvim_hlslens = true,\n nvim_lsp = true,\n nvim_navic = true,\n nvim_notify = true,\n nvim_tree = true,\n nvim_ts_rainbow = true,\n op_nvim = true,\n packer = true,\n polygot = true,\n rainbow_delimiters = true,\n startify = true,\n telescope = true,\n toggleterm = true,\n treesitter = true,\n trouble = true,\n vim_ultest = true,\n which_key = true,\n },\n\n options = {\n cursorline = false, -- Use cursorline highlighting?\n transparency = false, -- Use a transparent background?\n terminal_colors = true, -- Use the theme's colors for Neovim's :terminal?\n highlight_inactive_windows = false, -- When the window is out of focus, change the normal background?\n }\n})\n```\n\n

\n\n### Setting a theme\n\nCurrently, there are four themes in the colorscheme:\n\n- `onedark`\n- `onelight`\n- `onedark_vivid`\n- `onedark_dark`\n\nA theme can be set with:\n\n```lua\nvim.cmd(\"colorscheme onedark\")\n```\n\n### Configuring colors\n\nA theme has a palette of 13 core colors alongside many additional ones which are used for menus and git diffs for example. These colors can be found in the [themes](https://github.com/olimorris/onedarkpro.nvim/tree/main/lua/onedarkpro/themes).\n\nThe default colors can be changed by specifying the name of the color and a new hex code:\n\n```lua\nrequire(\"onedarkpro\").setup({\n colors = {\n red = \"#FF0000\"\n }\n})\n```\n\n**Specifying new colors**\n\nNew colors may be created which will then be merged into a theme's color palette:\n\n```lua\nrequire(\"onedarkpro\").setup({\n colors = {\n my_new_red = \"#f44336\",\n my_new_green = \"require('onedarkpro.helpers').darken('green', 10, 'onedark')\"\n }\n})\n```\n\n> **Note**: See the [helpers](#rainbow-helpers) section to understand how to use the color helpers.\n\nThese can then be used for custom highlight groups if desired:\n\n```lua\nrequire(\"onedarkpro\").setup({\n highlights = {\n Error = {\n fg = \"${my_new_red}\",\n bg = \"${my_new_green}\"\n },\n }\n})\n```\n\n**Specifying colors by theme or background**\n\nIt's possible to override default colors within a theme such as the `bg` color. This is a common question for those who wish to have a darker background than the default. Of course it would make sense to have different `bg` colors for the `onedark` and `onelight` themes. This can be achieved by specifying the theme name as a table, followed by the color:\n\n```lua\nrequire(\"onedarkpro\").setup({\n colors = {\n onedark = { bg = \"#FFFF00\" }, -- yellow\n onelight = { bg = \"#00FF00\" }, -- green\n }\n})\n```\n\nAlternatively, you can specify colors by the theme's background color:\n\n```lua\nrequire(\"onedarkpro\").setup({\n colors = {\n dark = { bg = \"#FFFF00\" }, -- yellow\n light = { bg = \"#00FF00\" }, -- green\n }\n})\n```\n\n### Configuring highlight groups\n\nThe [editor](https://github.com/olimorris/onedarkpro.nvim/tree/main/lua/onedarkpro/highlights/editor.lua), [syntax](https://github.com/olimorris/onedarkpro.nvim/tree/main/lua/onedarkpro/highlights/syntax.lua), [filetype](https://github.com/olimorris/onedarkpro.nvim/tree/main/lua/onedarkpro/highlights/filetypes) and [plugin](https://github.com/olimorris/onedarkpro.nvim/tree/main/lua/onedarkpro/highlights/plugins) files use a large array of highlight groups. Some examples of how you can customize or _override_ them:\n\n1. Using specific hex colors and styles:\n\n```lua\nrequire(\"onedarkpro\").setup({\n highlights = {\n Comment = { fg = \"#FF0000\", bg = \"#FFFF00\", italic = true }\n }\n})\n```\n\n2. Referencing the name of colors:\n\n```lua\nrequire(\"onedarkpro\").setup({\n highlights = {\n Comment = { fg = \"${my_new_red}\", bg = \"${yellow}\", italic = true }\n }\n})\n```\n\n3. Linking to other highlight groups:\n\n```lua\nrequire(\"onedarkpro\").setup({\n highlights = {\n Comment = { link = \"Substitute\" }\n }\n})\n```\n\n4. Extending existing highlight groups:\n\n```lua\nrequire(\"onedarkpro\").setup({\n highlights = {\n Comment = { underline = true, extend = true }\n }\n})\n```\n\n> **Note**: In the example above, an underline style has been applied to the existing `Comment` highlight group.\n\n#### Creating highlight groups\n\nYou can also create your own highlight groups:\n\n```lua\nrequire(\"onedarkpro\").setup({\n highlights = {\n MyNewHighlightGroup = { fg = \"${red}\" }\n }\n})\n```\n\nor, if you'd like to disable certain highlight groups:\n\n```lua\nrequire(\"onedarkpro\").setup({\n highlights = {\n [\"@lsp.type.comment\"] = {}\n }\n})\n```\n\n> **Note**: This can be useful to prevent LSP servers from applying semantic highlights\n\n#### Specifying highlight attributes by theme or background\n\nAs with colors, highlight attributes may be specified by using the theme name or the background color. For example:\n\n```lua\nrequire(\"onedarkpro\").setup({\n highlights = {\n Comment = {\n fg = { onedark = \"${yellow}\", onelight = \"${my_new_red}\" }\n }\n }\n})\n```\n\nAlternatively, by background color:\n\n```lua\nrequire(\"onedarkpro\").setup({\n highlights = {\n Comment = {\n fg = { dark = \"${yellow}\", light = \"${my_new_red}\" }\n }\n }\n})\n```\n\n#### Namespacing highlight groups\n\nNeovim supports the application of highlights to specific buffers via [namespaces](https://neovim.io/doc/user/api.html#api-extmark). To apply highlight groups to a specific namespace, use the `ns_id` key:\n\n```lua\nrequire(\"onedarkpro\").setup({\n highlights = {\n Comment = { ns_id = 1, fg = \"${light_gray}\" }\n }\n})\n```\n\n### Configuring styles\n\n> **Note**: For a list of available styles, please refer to the [Neovim documentation](https://neovim.io/doc/user/api.html#nvim_set_hl())\n\nStyles can be applied to highlight groups:\n\n```lua\nrequire(\"onedarkpro\").setup({\n highlights = {\n Comment = { italic = true },\n Directory = { bold = true },\n ErrorMsg = { italic = true, bold = true }\n }\n})\n```\n\nWithin the theme, collections of highlight groups have been grouped together into `styles`. For users who use monospaced fonts with nice italics, this can go someway to enhancing the aesthetic of a theme with minimal effort. These styles may be configured as shown in the example below:\n\n```lua\nrequire(\"onedarkpro\").setup({\n styles = {\n types = \"NONE\",\n methods = \"NONE\",\n numbers = \"NONE\",\n strings = \"NONE\",\n comments = \"italic\",\n keywords = \"bold,italic\",\n constants = \"NONE\",\n functions = \"italic\",\n operators = \"NONE\",\n variables = \"NONE\",\n parameters = \"NONE\",\n conditionals = \"italic\",\n virtual_text = \"NONE\",\n }\n})\n```\n\n### Configuring filetype highlighting\n\n> **Note**: Please see the [Contributing](https://github.com/olimorris/onedarkpro.nvim/blob/main/CONTRIBUTING.md) guide if you would like add support for new filetypes.\n\nThe theme supports opinionated highlighting for filetypes, just like the original Visual Studio Code theme. By default, all of the filetypes supported are loaded at runtime. The theme currently has support for:\n\n- `comment`\n- `go`\n- `html`\n- `java`\n- `javascript`\n- `json`\n- `lua`\n- `markdown`\n- `php`\n- `python`\n- `ruby`\n- `rust`\n- `scss`\n- `toml`\n- `typescript`\n- `typescriptreact`\n- `vue`\n- `xml`\n- `yaml`\n\n\nSpecific filetypes can be disabled as follows:\n\n```lua\nrequire(\"onedarkpro\").setup({\n filetypes = {\n markdown = false,\n ruby = false,\n }\n})\n```\n\nAlternatively, all of the filetypes can be disabled:\n\n```lua\nrequire(\"onedarkpro\").setup({\n filetypes = {\n all = false\n }\n})\n```\n\nOr, all of the filetypes can be disabled with a select few enabled:\n\n```lua\nrequire(\"onedarkpro\").setup({\n filetypes = {\n all = false,\n markdown = true,\n ruby = true,\n }\n})\n```\n\n**Adding or modifying filetype highlights**\n\nIt's likely that you'll wish to add additional filetype highlights or even change the defaults. This can be achieved by adding them as custom highlight groups in the theme:\n\n```lua\nrequire(\"onedarkpro\").setup({\n highlights = {\n [\"@field.yaml\"] = { fg = \"${blue}\", italic = true }\n }\n})\n```\n\nIn the example above, we have set the `field` treesitter highlight group to be blue, but only when the filetype is `yaml`. More information can be found via `:h treesitter-highlight-groups`.\n\nTo determine which highlight group is being applied in Neovim, see the [FAQ](#question-faqs) section.\n\n#### Configuring LSP semantic tokens\n\n> **Note**: Semantic tokens are only available in Neovim 0.9+ and with selected LSP servers.\n\nIn Neovim, some LSP servers may send tokens to the editor to allow for more intelligent highlighting such as variable scope; a feature which is impossible with Treesitter alone.\n\nSemantic highlighting in Neovim sees highlight groups set which have a priority greater than those of Treesitter and the base vim highlight groups (see `:h lsp-semantic_tokens` for more information). A full list of available semantic tokens can be found [here](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_semanticTokens).\n\nThe colorscheme has defined _some_ semantic tokens (to match the Visual Studio Code theme as closely as possible) and applies them as part of the filetype highlighting. To determine what tokens are available to set or override, use the `:Inspect` command.\n\nFinally, the colorscheme has defined some non-filetype tokens as a plugin, named `lsp_semantic_tokens`. See the section below for how to disable this.\n\n### Configuring plugins\n\n> **Note**: Please see the [Contributing](https://github.com/olimorris/onedarkpro.nvim/blob/main/CONTRIBUTING.md) guide if you would like add support for new plugins.\n\nBy default, all of the plugins supported by the theme are loaded at runtime. Specific plugins can be disabled as follows:\n\n```lua\nrequire(\"onedarkpro\").setup({\n plugins = {\n nvim_lsp = false,\n polygot = false,\n treesitter = false\n }\n})\n```\n\nAlternatively, all of the plugins can be disabled:\n\n```lua\nrequire(\"onedarkpro\").setup({\n plugins = {\n all = false\n }\n})\n```\n\nOr, all of the plugins can be disabled with a select few enabled:\n\n```lua\nrequire(\"onedarkpro\").setup({\n plugins = {\n all = false,\n nvim_lsp = true,\n treesitter = true\n }\n})\n```\n\n### Configuring options\n\n**Cursorline**\n\nCursorline highlighting is supported in the theme using a `cursorline` color (which may of course be overridden). This can be enabled with the following:\n\n```lua\nrequire(\"onedarkpro\").setup({\n colors = {\n cursorline = \"#FF0000\" -- This is optional. The default cursorline color is based on the background\n },\n options = {\n cursorline = true\n }\n})\n```\n\n**Transparency**\n\nThe theme supports transparent backgrounds:\n\n```lua\nrequire(\"onedarkpro\").setup({\n options = {\n transparency = true\n }\n})\n```\n\nBy setting the transparency option to true, the `Normal`, `Folded`, `SignColumn`, `Statusline` and `Tabline` groups will have `NONE` as the background color. Additional transparency may be achieved by overriding more highlight groups.\n\n**Terminal Colors**\n\nBy default, the colorscheme changes the colors for Neovim's `:terminal` to the current theme. This can be turned off if required.\n\n```lua\nrequire(\"onedarkpro\").setup({\n options = {\n terminal_colors = false\n }\n})\n```\n\n**Highlighting Inactive Windows**\n\nThe theme supports changing the color of the main window in Neovim when the focus is lost. For example, when a `telescope` or `packer` pop up appears:\n\n```lua\nrequire(\"onedarkpro\").setup({\n options = {\n highlight_inactive_windows = true\n }\n})\n```\n\n## :rainbow: Helpers\n\nThe theme comes with a set of helpers which enable you to interact with and modify colors. The helper file can be accessed via `require(\"onedarkpro.helpers\")`.\n\n**Using colors from a theme**\n\nIt can be useful to access a theme's colors for use within other plugins (such as your statusline) after its loaded. For this, the `get_colors` helper can be used:\n\n```lua\nlocal color = require(\"onedarkpro.helpers\")\n\nlocal colors = color.get_colors()\nprint(colors.purple) -- #c678dd (if using the Onedark theme)\n```\n\nWithout specifying a theme name, the helper will get the colors for the currently loaded theme. Alternatively, specify a theme name, such as `get_colors(\"onelight\")`.\n\nYou can also use the command `:OnedarkproColors` to open a scratch buffer with the colors from the currently loaded theme. This then allows a colorizer plugin to highlight the colors.\n\n> **Note**: Please ensure that the colorscheme loads ahead of any plugins which may wish to use the theme's colors.\n\n**Using colors _before_ a theme loads**\n\nWhilst the `get_colors` method is useful in most cases, it may be necessary to get a theme's colors before it has fully loaded. The common use case is for creating custom colors which are based on the theme's own palette and incorporating pback into the theme. For this the `get_preloaded_colors` method can be used:\n\n```lua\nlocal color = require(\"onedarkpro.helpers\")\n\nlocal colors = color.get_preloaded_colors()\nprint(colors.purple) -- #c678dd (if using the Onedark theme)\n```\n\n> **Note**: This will only output the theme's core color palette and not any generated colors.\n\n**Darken/Lighten/Brighten colors**\n\nThe theme also contain helpers `darken`, `lighten` and `brighten`, to allow you to modify custom colors or the theme's own. All three helpers follow the same format and take three parameters:\n\n- color (string) - The name of the color to load (if specifying a theme) or a hex value\n- amount (number) - The amount to darken/lighten/brighten the color by (range from -100 to 100)\n- theme (string) (optional) - The name of the theme to load a color from\n\nTo use this in practice:\n\n```lua\nlocal color = require(\"onedarkpro.helpers\")\n\n-- Load the red color from the onedark theme and lighten it by an amount of 7\nprint(color.lighten(\"red\", 7, \"onedark\")) -- #e68991\n```\n\nAlternatively:\n\n```lua\nlocal color = require(\"onedarkpro.helpers\")\n\n-- Darken Red1 by an amount of 10\nprint(color.darken(\"#FF0000\", 10)) -- #cc0000\n```\n\nOf course, you're likely to wish to modify colors before the colorscheme loads. There are a number of ways to accomplish this and the most efficient is to pass a function (as a string) to the `colors` table in the theme's configuration:\n\n```lua\nrequire(\"onedarkpro\").setup({\n colors = {\n dark_red = \"require('onedarkpro.helpers').darken('red', 10, 'onedark')\",\n },\n highlights = {\n CustomRedHighlight = {\n fg = \"${dark_red}\",\n },\n }\n})\n```\n\nThis prevents the theme from trying to resolve the color before the whole of the configuration has been parsed. This also ensures that the startup time for the theme remains small too.\n\n## :electric_plug: Supported Plugins\n\nThe theme supports the following plugins:\n\n- [aerial.nvim](https://github.com/stevearc/aerial.nvim) (`aerial`)\n- [barbar.nvim](https://github.com/romgrk/barbar.nvim) (`barbar`)\n- [Copilot.vim](https://github.com/github/copilot.vim) (`copilot`)\n- [Dashboard](https://github.com/glepnir/dashboard-nvim) (`dashboard`)\n- [diffview.nvim](https://github.com/sindrets/diffview.nvim) (`diffview`)\n- [flash.nvim](https://github.com/folke/flash.nvim) (`flash.nvim`)\n- [gitsigns.nvim](https://github.com/lewis6991/gitsigns.nvim) (`gitsigns`)\n- [Hop.nvim](https://github.com/phaazon/hop.nvim) (`hop`)\n- [Indent Blankline](https://github.com/lukas-reineke/indent-blankline.nvim/tree/lua) (`indentline`)\n- [leap.nvim](https://github.com/ggandor/leap.nvim) (`leap`)\n- [lspsaga.nvim](https://github.com/glepnir/lspsaga.nvim) (`lsp_saga`)\n- LSP Semantic tokens (`lsp_semantic_tokens`)\n- [marks.nvim](https://github.com/chentau/marks.nvim) (`marks`)\n- [mini.indentscope](https://github.com/echasnovski/mini.indentscope) (`mini_indentscope`)\n- [Neotest](https://github.com/nvim-neotest/neotest) (`neotest`)\n- [neo-tree](https://github.com/nvim-neo-tree/neo-tree.nvim) (`neo_tree`)\n- [nvim-cmp](https://github.com/hrsh7th/nvim-cmp) (`nvim_cmp`)\n- [nvim-bqf](https://github.com/kevinhwang91/nvim-bqf) (`nvim_bqf`)\n- [nvim-dap](https://github.com/mfussenegger/nvim-dap) (`nvim_dap`)\n- [nvim-dap-ui](https://github.com/rcarriga/nvim-dap-ui) (`nvim_dap_ui`)\n- [nvim-hlslens](https://github.com/kevinhwang91/nvim-hlslens) (`nvim_hlslens`)\n- [nvim-lspconfig](https://github.com/neovim/nvim-lspconfig) (`nvim_lsp`)\n- [nvim-navic](https://github.com/SmiteshP/nvim-navic) (`nvim_navic`)\n- [nvim-notify](https://github.com/rcarriga/nvim-notify) (`nvim_notify`)\n- [nvim-tree](https://github.com/kyazdani42/nvim-tree.lua) (`nvim_tree`)\n- [nvim-ts-rainbow](https://github.com/p00f/nvim-ts-rainbow) (`nvim_ts_rainbow`)\n- [nvim-ts-rainbow2](https://github.com/HiPhish/nvim-ts-rainbow2) (`nvim_ts_rainbow2`)\n- [op.nvim](https://github.com/mrjones2014/op.nvim) (`op_nvim`)\n- [packer.nvim](https://github.com/wbthomason/packer.nvim) (`packer`)\n- [polygot](https://github.com/sheerun/vim-polyglot) (`polygot`)\n- [startify](https://github.com/mhinz/vim-startify) (`startify`)\n- [telescope.nvim](https://github.com/nvim-telescope/telescope.nvim) (`telescope`)\n- [toggleterm.nvim](https://github.com/akinsho/toggleterm.nvim) (`toggleterm`)\n- [Treesitter](https://github.com/nvim-treesitter/nvim-treesitter) (`treesitter`)\n- [Trouble](https://github.com/folke/trouble.nvim) (`trouble`)\n- [Vim Ultest](https://github.com/rcarriga/vim-ultest) (`vim_ultest`)\n- [Which Key](https://github.com/folke/which-key.nvim) (`which_key`)\n\n\n\n## :camera_flash: Comparison Screenshots\n\n> **Note**: Every effort has been made to get the colorscheme as close to the original as possible. If you notice any discrepencies, please raise a [discussion](https://github.com/olimorris/onedarkpro.nvim/discussions/new?category=color-match).\n\n**Python**\n\n $\"Python\"$ \n\n**Lua**\n\n $\"Lua\"$ \n\n**TypeScript**\n\n $\"TypeScript\"$ \n\n**Javascript/React**\n\n $\"Javascript/React\"$ \n\n\n\n## :gift: Extras\n\n**Lualine**\n\nThe theme has Lualine support out of the box for all of its themes. This can be found in the [Lualine folder](https://github.com/olimorris/onedarkpro.nvim/tree/main/lua/lualine/themes).\n\n**Toggling between themes**\n\nTo enable the easy switching between dark and light colorschemes, the following helper function could be used:\n\n```lua\nfunction ToggleTheme()\n if vim.o.background == \"dark\" then\n vim.cmd(\"colorscheme onelight\")\n else\n vim.cmd(\"colorscheme onedark\")\n end\nend\n```\n\n## :question: FAQs\n\n**I want to change X highlight group but I don't know what it is. How do I find out?**\n\nIf you're using Neovim 0.9+, the `:Inspect` command is available.\n\nIf you're on an earlier version of Neovim and are using Treesitter, install [Playground](https://github.com/nvim-treesitter/playground) as this gives you access to the powerful `:TSHighlightCapturesUnderCursor` command. This shows any Treesitter or syntax highlight groups under the cursor.\n\n**I've noticed some differences between the theme and Visual Studio Code. Why is this?**\n\nI've tried to ensure that the theme resembles the original Visual Studio Code theme as much as possible. To that end we have carefully applied custom Treesitter queries to certain filetypes as well as mapped LSP semantic token colors. If you notice any differences, please raise a [discussion](https://github.com/olimorris/onedarkpro.nvim/discussions/new?category=color-match) with supporting screenshots.\n\n## :clap: Credits\n\nThe following colorschemes serve as inspiration:\n\n- [One Dark Pro](https://github.com/Binaryify/OneDark-Pro) - The inspiration for this colorscheme\n- [Catppuccin/nvim](https://github.com/catppuccin/nvim) - For the genius idea of hashing and caching and pushing the envelope of Neovim colorschemes and the kind PRs\n- [Nightfox](https://github.com/EdenEast/nightfox.nvim) - For the original code structure\n- [GitHub nvim theme](https://github.com/projekt0n/github-nvim-theme) - For the logo inspiration\n","dotfyleShieldAddedAt":null,"stars":593,"lastSyncedAt":"2023-11-28T02:21:19.811Z","addedLastWeek":2}}},{"id":"04cecece-8b3c-471a-862d-43135a051bc3","title":"fix!: #195 do not extend hl groups by default","text":"fix!: #195 do not extend hl groups by default\n\nInstead, give users the option to add `extend = true`","type":"breaking-change","createdAt":"2023-06-22T22:40:07.122Z","breakingChange":{"id":6,"postId":"04cecece-8b3c-471a-862d-43135a051bc3","pluginId":215,"externalUrl":"https://github.com/olimorris/onedarkpro.nvim/commit/0b53cb1a89f502d10934a4afc8a276a797330f17","sha":"0b53cb1a89f502d10934a4afc8a276a797330f17","plugin":{"id":215,"owner":"olimorris","name":"onedarkpro.nvim","type":"github","source":"awesome-neovim","category":"colorscheme","link":"https://github.com/olimorris/onedarkpro.nvim","shortDescription":"🎨 Atom's iconic One Dark theme, for Neovim. Fully customisable, with Treesitter, LSP semantic token support and a light variant","createdAt":"2023-03-22T19:35:21.592Z","readme":"\n\n

\n $\"OneDarkPro.nvim\"$ \n

\n\n

OneDarkPro.nvim

\n\n

\n\n\n\n\n

\n\n

\n\n## :icecream: Themes\n\n> **Note**: All bolds and italics in the screenshots below are [completely customisable](#configuring-styles)\n\n

Onedark $\"onedark\"$

Onelight $\"onelight\"$

Onedark Vivid $\"onedark$

Onedark Dark $\"onedark$

Click to see the default configuration