hydra.nvim VS trouble.nvim

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

Does anyone know if it's possible to copy the LSP diagnostics (which currently is being displayed using folke/trouble to the quickfix window?

A newbie here, I used jose-elias-alvarez/null-ls.nivm for diagnostics and formatting, but I recently discovered folke/trouble.nvim and for me, it seems like a better option However, I don't know if it supports formatting and linting, I don't even know if it is an alternative to null-ls. So I need your help, can trouble.nvim replace null-ls? If not, can I use both of them simultaneously?

Trouble

Looking at the screenshot here for example https://github.com/folke/trouble.nvim they show errors both in the gutter and underlined.

All you need is just the LSP working (with linter, formatter and diagnostics) and telescope. Seriously, telescope is the GOAT, way faster than a file tree, you end up using the filetree only to move, create and delete files/folders but if it's just for that, you might as well use the terminal instead. For the LSP, it's not only autocompletion and hints at hover but formatting and diagnostics. I use lsp-zero + null-ls + trouble. I exposed all of the keybindings on those so I can at least open my own configs for guidance. Oh yeah, having treesitter is probably a must too, and it has no keybindings on its base form.

I am referring this as well as this this plugin.

Trouble: https://github.com/folke/trouble.nvim

Trouble is so good for finding errors easily. For testing I use jest so I haven't had too many issues. What do you test with?

I like trouble.nvim

I guess LazyVim uses https://github.com/folke/trouble.nvim for it. I should config it to not including errors regarding standardization.