[mini.jump2d] Question time action in single_character

[vtmx]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.jump2d

Question

First of all, I would like to express my immense gratitude to Chasnovski and the Mini team for these incredible tools that make a huge difference in the daily workflow of many developers.

First of all, I would like to express my immense gratitude to Chasnovski and the Mini team for these incredible tools that make a huge difference in the daily workflow of many developers.

Recently I've been switching most of the plugins I use to their mini equivalents. And one of my favorite plugins, hop, has been discontinued. I still use it very well, but I also installed MiniJump2d to do some testing.

I notice a slight delay before the first message appears to start typing. Can someone confirm if this is normal or if there's an option to increase the speed?

-- A little delay to show 'Enter single character to search'
vim.keymap.set(
  'n', 's', function()
    require('mini.jump2d').start(require('mini.jump2d').builtin_opts.single_character)
  end
)

-- Works perfect
map(
  'n', 'S', function() require('mini.jump2d').start() end
)

[echasnovski]

First of all, I would like to express my immense gratitude to Chasnovski and the Mini team for these incredible tools that make a huge difference in the daily workflow of many developers.

First of all, I would like to express my immense gratitude to Chasnovski and the Mini team for these incredible tools that make a huge difference in the daily workflow of many developers.

Thank you for kind words! Especially expressed twice :)

I notice a slight delay before the first message appears to start typing. Can someone confirm if this is normal or if there's an option to increase the speed?

There are two possible things possibly happening here at the same time:

• If you by "first message" you mean the (mini.jump2d) Enter single character to search, then this is a helper message displayed after one second of user inactivity. It should be possible to start pressing a single character immediately after initiating the jump, i.e. before the message is shown.

• If you do not see the labels showing when pressing a single character immediately after s, then it is the s itself the problem. It probably conflicts with default mappings from 'mini.surround' (and other planned 'mini.nvim' modules in the future). Those are sa, sd, etc. What happens is that after pressing s Neovim is not yet sure what you want to do: either to execute s immediately or wait for the next possible key press for sa, sd, etc.

  The solution here can come in two ways: use different key for jumping (one of the reasons <CR> is the default) or different keys for 'mini.surround'. The more future proof way is to use different key for jumping.

I would also point out that 'mini.jump2d' is planned to be redesigned soon-ish (see #1818). In particular, the equivalent of single_character will be the default spotter and sj will be the default key to start jumping.

Hope this helps.

[vtmx]

Thank you for your reply. I'm glad we'll have news. I did some tests modifying the mapping for the new key and also testing directly with the command, and I continued to notice the delay.

:lua require('mini.jump2d').start(require('mini.jump2d').builtin_opts.single_character)

Then I noticed that what's actually taking a little time is the appearance of the message "(mini.jump2d) Enter single character to search", but, if I start typing after pressing the mapped keys, it works.

[echasnovski]

Yes, that message is purely informational to remind user to press a key. The effect will still be there if key is pressed before the information message is shown.