nvim-window VS hydra.nvim

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.

return require('packer').startup { function(use) use 'wbthomason/packer.nvim' -- 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'} -- Indentation tracking use { 'lukas-reineke/indent-blankline.nvim', } -- Completion and linting use 'neovim/nvim-lspconfig' use {'hrsh7th/nvim-compe', 'onsails/lspkind-nvim'} use 'hrsh7th/vim-vsnip' use 'rafamadriz/friendly-snippets' use 'windwp/nvim-autopairs' use 'nvim-lua/lsp-status.nvim' -- use 'dense-analysis/ale' -- misc use 'tpope/vim-sleuth' use { "folke/which-key.nvim", config = function() require("which-key").setup{} end } use {'folke/zen-mode.nvim', config = function() require("zen-mode").setup {} end} use 'tpope/vim-commentary' use 'glepnir/dashboard-nvim' use 'rafcamlet/nvim-luapad' -- colors -- use 'https://git.konart.dev/konart/ciapre.vim' use '~/build/personal/ciapre.vim' -- UI use { 'glepnir/galaxyline.nvim', branch = 'main', -- your statusline -- config = function() require'settings/plugings' end, -- some optional icons requires = {'kyazdani42/nvim-web-devicons', opt = true} } use {'akinsho/nvim-bufferline.lua', requires = {'kyazdani42/nvim-web-devicons', opt = true}} end }

-- 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'}

similar to hydra?

A Hydra mode to quickly manipulate and run cells

Possibly hydra, which everything from submodes to a more customized which-key. Works really well for making a telescope menu or a DAP mode.

The other way, that I use for some navigation functions is using hydra.nvim. You can basically create little 'submodes' to group related functionality with quicker mappings. Like after [hjkl] you can just hit hjkl to keep moving around, and then hitting esc or just any key not in the submode to leave it.

I use this function to exclude the currently focused floating window and ignore floating windows of some plugins (in this case only the popup from hydra.nvim is ignored):

There is also https://github.com/anuvyklack/keymap-layer.nvim used by https://github.com/anuvyklack/hydra.nvim

This suggestion and similar (like [[ and ]] to repeat latest target) did come up. I feel like that is the "responsibility" of something like anuvyklack/hydra.nvim or the (some time eventually) planned 'mini.nvim' alternative.

I installed hop but can't get used to it and just hold j/k/W/B as someone commented higher. Btw, for plaintext files this can be useful, even without hydra: https://github.com/anuvyklack/hydra.nvim/wiki/Quick-words

Of course, each case is different, but for making repeatable mappings there is anuvyklack/hydra.nvim. Or in some cases you can avoid this by choosing appropriate mappings (like Ctrl + arrows for window resizing which doesn't require repeating several keystrokes for a single operation).

I don't quite know what I am looking at in your screenshot (I haven't used emacs either though), but I use hydra.nvim and I can get a similar end result with it