vim-code-dark VS feline.nvim

I'm new to Neovim stuff so I could have gone wrong in my configuration but everything seems working. For now, I've switched to tomasiser/vim-code-dark since it supports treesitter out of box but the module mismatch issue I'd mentioned is still in vim-code-dark and every other colorscheme I've tried. Is this a treesitter bug? Any advice would be appreciated

try out this theme instead, it might work better: https://github.com/tomasiser/vim-code-dark

I made a port of vim code dark, which is the vscode dark+ default theme.

codedark? https://github.com/tomasiser/vim-code-dark

FYI, vim-code-dark, a vscode dark+ port, has been around since 2017.

tomasiser/vim-code-dark Dunno why, but I just love this theme

I am using treesitter for typescript, and now markdown too. I want the standard VS Code colour scheme you can see at https://vscode.dev/github/Microsoft/vscode. I am using https://github.com/tomasiser/vim-code-dark, but there is also https://github.com/Mofiqul/vscode.nvim available.

The picture is Neovim using https://github.com/tomasiser/vim-code-dark and https://microsoft.github.io/vscode-codicons/

https://github.com/feline-nvim/feline.nvim is archived since 17 Feb 2023

I'm using feline.nvim but this question isn't specific to feline.

I use feline to generate my statusline and my winbar. This is imho the best statusline plugin for neovim in terms of configuration, truncation, default providers etc.

The "look" you're looking for is given by a bunch of plugins: - OneDark.nvim as colorscheme - TS Rainbow for rainbow brackets - BarBar for bufferline - Nvim Devicons and NerdFonts to view file icons - NvimTree as a file manager - Indent Blankline to show indentation guides - CompetiTest with vertical split UI - Feline as statusline plugin. In the screenshot feline is configured with a custom theme. As you can see statusline is different for CompetiTest buffers: a different statusline can be configured for every different filetype using conditional_config.

We have now migrated from feline to heirline

Pretty sure it isn't. Siduck used to use feline.nvim then later moved onto creating their own statusline that is specific to NvChad. You can find it here.

Hi! I'm a big fan of the feline plugin to describe a statusline. It provides a very powerful api to create your own components, which can be used in the statusline. But also, I like a way of the lualine, in which we can separate the schema of the statusline and used components. So, I've tried to combine these advantages in one place and wrote an extension for feline: dokwork/feline-theme.

Author of Feline.nvim and also the winbar PR here. I want to inform everyone who uses Feline that it now has support for winbar.

Packer failed to update feline.nvim, and I saw that it's been moved to https://github.com/feline-nvim/feline.nvim.

Hello, author of Feline.nvim here. I'll get straight to the point. A while ago I started using Semantic Versioning for Feline.nvim as it seemed like a good idea at that time. However, as time went by, it just became more and more of a hassle to release new versions, especially after development of Feline.nvim slowed down and it just needed minor bugfixes. I feel like now it's more hassle than it's worth. So I'm switching back to using a rolling-release model. From now on, the master branch will contain the latest changes. The development branch is deprecated and all development branch users need to switch to the master branch.