marks.nvim VS which-key.nvim

Hello, one day (today) I got tired of using built-in `marks` command output, so I wrote a simple function, which displays all my marks in my editor. For now I don't want to use plugins like marks.nvim or harpoon by Primeagen to get myself into NeoVim Lua API a bit. How can I improve it, for example, to show information humanized, or go to mark by pressing on it, etc?

I don't have this workflow to cycle between 3 or 4 files, but I think "marks" like plugins could help with this: marks.nvim, harpoon, etc

list all marks to jump to (I use marks.nvim but any equivalent would do)

At least for marks it helped me to try this plugin: https://github.com/chentoast/marks.nvim

marks.nvim. In the sign column it shows your marks.

Issues like this https://github.com/chentoast/marks.nvim/issues/62 (high CPU) give me cause for concern with Marks, although, by the looks of it, it is a problem with Neovim in general.

I'm also using marks.nvim which helps me see where the marks exactly are.

Harpoon plugin was written for this exact scenario, but I try to use global marks for this. I use marks.nvim plugin to signify lines with a mark, Teleform marks, and which-key.nvim (w/mark preview).

I'm using marks.nvim to show marks in the gutter, and every time I format using lua vim.lsp.buf.format(), all my marks get deleted. Is there any way to prevent this or is just a bug?

I use chentoast/marks.nvim, which-key.nvim and :telescope marks. This combination of plugins makes working with marks much easier.

There is a well known plugin for neovim to do this kind of behavior. You can even create your own hotkeys into that plugin and will help you navigate and memorize different hotkeys for the editor. The plugin is called whichkey, and this is their github https://github.com/folke/which-key.nvim

The menu most certainly comes from folke/which-key.nvim. Take a look into part of your config which sets it up.

By default, most of nvim packages have WhichKey plugin which shows popup with available commands. For instance, you press space or g and what for a second:

One of the recent innovations in the Vim space that I've appreciated a lot is which-key by folke for Neovim: https://github.com/folke/which-key.nvim

It makes keybindings in vim discoverable, it's quite magical. For example, press g and get a table of all the various commands that follow from there. Press mapleader and get a table of various commands from there, etc.

>The problem with that is that for some rarely used action one forgets...

Install https://github.com/folke/which-key.nvim and you will always have a popup that will tell you what keys to use next.

https://github.com/folke/which-key.nvim - it's like a cheat sheet in neovim!

folke/which-key.nvim will help with you with your key maps.

I recently started actively using which-key plugin that shows the contents of all registers when pressing ".

3) I'd recommend using Telescope, more specifically, :Telescope keympas. There's also which-key, which might be more intuitive, but I haven't used it.