nvim-dotfiles-kitty VS nvim-window

If you are using Kitty, you can check my configuration where I mix hologram.nvim with Telescope.

Here is mine

I use treesitter for syntax-highlight, Golsp, EFM for lint and code formatter (goimport, gofumpt), luasnip + friendly-snippets for snippets. My .dotfile https://github.com/Nguyen-Hoang-Nam/nvim-dotfiles

I'm using https://gitlab.com/yorickpeterse/nvim-window to jump between neovim's windows (mapped to w).

What is the difference, in your opinion, or maybe selling point between this plugin and the other ones like it? For example nvim-window and nvim-window-picker, to name the Lua ones that I can think of.

Now, Neovim will wait for users input inside hydra if it is required: for example, for nvim-window and so on.

A while back I wrote an equivalent (but probably much simpler and more limited) plugin for NeoVim: https://gitlab.com/yorickpeterse/nvim-window.

hey look! https://gitlab.com/yorickpeterse/nvim-window

I've found nvim-window and vim-win, which sort of provide this behaviour.

-- hacks use 'tjdevries/astronauta.nvim' -- git use {'tpope/vim-fugitive'} --use 'airblade/vim-gitgutter' use {'lewis6991/gitsigns.nvim', requires = {'nvim-lua/plenary.nvim'}} use 'tweekmonster/startuptime.vim' -- text manipulation use 'tpope/vim-surround' use 'mattn/emmet-vim' -- navigation use {'kyazdani42/nvim-tree.lua'} use 'phaazon/hop.nvim' use {'https://gitlab.com/yorickpeterse/nvim-window'} use { 'nvim-telescope/telescope.nvim', requires = {{'nvim-lua/popup.nvim'}, {'nvim-lua/plenary.nvim'}} } use { 'camspiers/snap' } use { "folke/trouble.nvim", requires = "kyazdani42/nvim-web-devicons", config = function() require("trouble").setup{} end } -- Highlights use { 'nvim-treesitter/nvim-treesitter', requires = { 'nvim-treesitter/nvim-treesitter-refactor', 'nvim-treesitter/nvim-treesitter-textobjects' }, -- config = [[require('settings/plugins/treesitter')]] } use {'nvim-treesitter/playground'}