mini.clue: Is there a way to enter submode with a function?

[aShabat]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.clue

Question

Is there a way to write a function or user command that enters a submode?

I added to my config a submode for moving between git hunks and staging them. I'm trying to add a way to open nvim already in this submode, for smoother work with lazygit.

I've tried using nvim_input to input submode's prefix, or to read first keypress and input prefix..keypress, but this doesn't trigger mini.clue so it doesn't leave me in submode

[echasnovski]

I've tried using nvim_input to input submode's prefix, or to read first keypress and input prefix..keypress, but this doesn't trigger mini.clue so it doesn't leave me in submode

Using vim.api.nvim_input works for me. For example, with the submode_resize enabled interactively executing :lua vim.api.nvim_input('<C-w>>') increases width once and starts the submode.

What 'mini.clue' setup do you have and what nvim_input input have you tried?

I'm trying to add a way to open nvim already in this submode, for smoother work with lazygit.

This may be another source of issues. For example, make sure that 'mini.clue' is not lazy loaded (i.e. is set up before nvim_input() call).

[aShabat]

I retested and now nvim_input works. Not sure what I did wrong before.

This may be another source of issues. For example, make sure that 'mini.clue' is not lazy loaded (i.e. is set up before nvim_input() call).

This might be my issue. I wrote user command that calls vim.api.nvim_input(prefix) and it now works when called in session, but when starting nvim with -c option submode doesn't work.

[echasnovski]

Yeah, then it is the issue of properly setting up config for a startup.

[aShabat]

Looking into plugin specs for mini.nvim I don't think it's lazy loaded, but I also tried to rewrite command so it calls only after mini.nvim is loaded.

vim.api.nvim_create_user_command('GitHunksInit', function()
    vim.api.nvim_create_autocmd('User', {
        pattern = 'LazyLoad',
        callback = function(args)
            if args.data == 'mini.nvim' then
                vim.notify '"mini.nvim" is loaded'
                vim.api.nvim_input ' gg'
            end
        end,
    })
end, {})

but it doesn't work

[echasnovski]

Sorry, can't help you here. Don't really have experience with 'lazy.nvim' and how to ensure that it loads something in order.

With this command approach, the command itself might be called after a target 'LazyLoad' event has already triggered.

[aShabat]

Ok, thank you!

[aShabat]

Sorry for bothering again, but there is one thing I don't understand.
I made this example script

vim.keymap.set('n', ' nn', 'j')
require('mini.clue').setup{
    triggers = {
        {mode = 'n', keys = ' n'},
    },
    clues = {
        {mode = 'n', keys = ' nn', postkeys = ' n'},
    },
}

After this, if I run vim.api.nvim_input' n' it does wait for next input and works like a submode. But if I run vim.api.nvim_input' nn' it moves down once, but doesn't stay in submode.

As you said, submode_resize works as expected, but for some reason submodes that I create myself don't.

[echasnovski]

After this, if I run vim.api.nvim_input' n' it does wait for next input and works like a submode. But if I run vim.api.nvim_input' nn' it moves down once, but doesn't stay in submode.

That's probably related to the fact that triggers are implemented through buffer-local mappings. So as there is a buffer-local mapping <Space>n, using nvim_input with it as input works. However, in the same situation, two consecutive calls like nvim_input(' n') and nvim_input('n') don't work (even with vim.loop.sleep(1) in the middle.

Honestly, this is a territory of studying by trial and error about the exact behavior Neovim processes key presses. And this logic mostly comes from Vim, so might be (and often is) unintuitive. This was the experience during 'mini.clue' development and I am glad it is at least in the state that works interactively 😅

[aShabat]

I see. For now I solve it by waiting for for any keypress before calling nvim_input(prefix). Maybe will eventually figure out some more satisfying solution.