A faithful Neovim port of the Night Owl VSCode theme with extended Treesitter and semantic token support.
night-owl.nvim is a Neovim colorscheme that meticulously recreates Sarah Drasner's popular Night Owl theme from VSCode. It provides a visually pleasing and accurate syntax highlighting experience for developers who prefer the Night Owl aesthetic within Neovim's modern ecosystem.
Neovim users who are familiar with and enjoy the Night Owl theme from VSCode and want a high-fidelity port. It is particularly suited for developers working with JavaScript, TypeScript, JSON, Markdown, Lua, Vimscript, R, Python, and Bash.
Developers choose this over other Night Owl ports because it prioritizes fidelity to the original VSCode theme while leveraging Neovim's advanced features like Treesitter and semantic tokens for more accurate and granular syntax highlighting. It also includes unique features like inactive window dimming and built-in support for popular Neovim plugins.
🦉 🌌 Night Owl colorscheme implementation for Neovim with support for Treesitter and semantic tokens
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses extended Treesitter queries and semantic token support to closely match the original Night Owl theme, with comparison screenshots showing fewer discrepancies than alternatives like haishanh/night-owl.vim.
Includes ready-made styles for popular plugins such as nvim-tree, lualine.nvim, and gitsigns.nvim, reducing the need for manual configuration and ensuring visual consistency.
Implements inactive window dimming through autocommands, automatically changing the background color when Neovim is not active to improve concentration, as detailed in the after/plugin files.
Offers configuration options for bold, italics, underlines, undercurls, and transparent backgrounds, allowing users to tweak the theme to their preferences via a simple setup function.
The README explicitly lists languages like Rust and Ruby as 'coming soon,' indicating incomplete support that may not meet the needs of developers working in those ecosystems.
The 'Requirements' section is marked as 'TODO,' leaving users unsure about necessary dependencies or compatibility issues, which could lead to setup frustrations.
Heavily relies on Neovim-specific features such as Treesitter and semantic highlighting, making it incompatible with Vim and potentially brittle with future Neovim updates.