nord.nvim VS vim-fugitive

There are also non-purple-ish color schemes coming right after top 5: - sainnhe/everforest - sainnhe/gruvbox-material and ellisonleao/gruvbox.nvim - navarasu/onedark.nvim - marko-cerovac/material.nvim (except one variation) - shaunsingh/nord.nvim

I like to apply Nord liberally to everything. I’ve found this one to be much better than the official nord package. shaunsingh/nord.nvim

I use nord.nvim and it works great.

Neovim supports any Vim theme, but I focussed on exclusive extensions where sensible, like it is in the case of colour schemes. In fact, an acclaimed addition to the 0.5 Neovim release was the support for tree-sitter, which provides advanced code parsing functionalities. That means it offers, among other mouth-filling wizardries, support for better syntax highlighting. The nvim-treesitter repository lists supported languages and compatible themes. I found shaunsingh/nord.nvim, avarasu/onedark.nvim, sainnhe/edge and rose-pine/neovim simply irresistible.

I'm trying to rewrite nord.nvim with nvim_set_hl, but I'm running into a few issues.

Hi everyone! I’m happy to announce that CosmicNvim now includes first-class support for 4 additional themes on top of the default for a total of 5 themes to choose from! The current selection: - [Catppuccino](https://github.com/Pocco81/Catppuccino.nvim) - [Gruvbox](https://github.com/ellisonleao/gruvbox.nvim) - [Rose-pine](https://github.com/rose-pine/neovim) - [Nord](https://github.com/shaunsingh/nord.nvim) - [Tokyonight](https://github.com/folke/tokyonight.nvim) Repo: https://github.com/mattleong/CosmicNvim (⭐️’s are very appreciated!) I’ve previously said that I wouldn’t implement first class theme support for CosmicNvim outside of the default theme… Well, I guess I changed my mind. 😅 For one, it’s probably been the most requested feature. For another, I want to be able to swap and play around with themes easily as well. My initial reason for _not_ wanting to include additional theme support was because I was worried about what sort of complexity it would bring. Turns out it’s not so bad and doesn’t overly bloat the codebase. If you have any suggestions for themes you’d like to see implemented, please feel free to drop them in the open [issue](https://github.com/mattleong/CosmicNvim/issues/25)!

the only reason I do some git stuff in vim and not _always_ in the shell, is because tpope is very thoughtful and fugitive.vim provides nice ways to deal with hunks or hunk partials (visually selecting a range within a hunk, for i.e.)

https://github.com/tpope/vim-fugitive/blob/master/doc/fugiti...

I agree, navigating blame history is incredibly useful, if only to save you from asking the wrong person about a particular change.

Vim's Fugitive[1] can do this and also in Textmate to. So I would hope that most editor git plugins can.

1. https://github.com/tpope/vim-fugitive

Git: vim-fugitive and gitsigns.nvim

You'll want to invest the time in learning Magit, which will change your life once you get the hang of it (and I was a heavy user of Fugitive in Vim previously!), and it's unlikely you'll find a better integration with GDB anywhere else on the planet than with Emacs, though I can't say that empirically. You just need to take the plunge and start learning it, then cut over and take the hit in productivity one day when you're feeling adventurous. You'll ultimately become far more powerful than you've ever been. Especially if you delve into elisp over time. I use Spacemacs, which is bloated and has bugs, but it has so many features that I haven't undertaken the massive endeavor to replace it from scratch yet.

For an option that works on Vim, if you already use tpope's vim-fugitive, there's vim-rhubarb (for GitHub) and fugitive-gitlab.vim (for GitLab).

I replace vim-fugitive with :! git

The only thing I truly miss from Emacs is [Magit](https://magit.vc/) since I still consider it the best git wrapper available. It is just too good. Unfortunately [Neogit](https://github.com/TimUntersberger/neogit) is not quite there yet although I hope it makes it at some point. I didn't like [Fugitive]https://github.com/tpope/vim-fugitive), but I ended up finding a good enough workaround by using [Lazygit](https://github.com/jesseduffield/lazygit) through [Toggleterm](https://github.com/akinsho/toggleterm.nvim).

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

Edit: je viens de trouver [https://github.com/tpope/vim-fugitive de Val