Changing nvim settings when IM is active?

[davinosuke]

I'm not sure if this is something that can be done already, or if it needs some new feature added. I want to be able to modify or toggle nvim settings when the IM mode changes.

In my neovim config have an autocommand to exit insert mode automatically after 20 seconds of inactivity. It works by changing the updatetime option when entering or exiting insert mode.

When working directly on English text this is fine, but when I use my Japanese IME (fcitx5/mozc) it sometimes exits when I am still typing. Sometimes it takes me a while to find the kanji I need in the dropdown, and that use is not detected as activity by CursorHoldI.

What I think I should do then, is increase or disable the timeout when the IME is active; either directly through the plugin, or by somehow detecting the setting in the autocommand. Increasing updatetime to 10000 or so would probably do the job.

However, I do not know how to do either of these, so any assistance would be welcome. Thanks.

This is the autogroup I am using:

vim.api.nvim_create_augroup("exitinsert", { clear = true })
api.nvim_create_autocmd( {'CursorHoldI'}, {
    group = "exitinsert",
    callback = function()
        vim.cmd.stopinsert()
    end,
})
api.nvim_create_autocmd( {'InsertEnter'}, {
    group = "exitinsert",
    callback = function()
        restore_updatetime = vim.o.updatetime
        vim.o.updatetime = 20000
    end,
})
api.nvim_create_autocmd( {'InsertLeave'}, {
    group = "exitinsert",
    callback = function()
      vim.o.updatetime = restore_updatetime
    end,
})

And my im-select configuration.:

config = function()
    require("im_select").setup({
        default_im_select  = "keyboard-jp-OADG109A",
        default_command = "fcitx5-remote",
    })
end,

[keaising]

I think the problem you met is not about im-select.nvim, but CursorHoldI doesn't detect your input when CJK IM is working. You can check this detail in CursorHoldI implementation fo neovim's document/source code.

For im-select.nvim, you can find that it only detect event like InsertEnter and InsertLeave, it will not raise the problem you met, because it will not call InsertEnter or InsertLeave, it only receives these events.

An approach you can check if the CursorHoldI raise the problem: add some debug info in this autocmd and observe the autocmd's behavior:

api.nvim_create_autocmd( {'CursorHoldI'}, {
    group = "exitinsert",
    callback = function()
        vim.cmd.stopinsert()
    end,
})

[keaising]

If you think this plugin raise any problem, you can also add some log and debug in your local environment, such as https://github.com/keaising/dotfile/blob/2938975ba9e3d9a4f499afcf8b5406edf533b2e4/nvim/.config/nvim/lua/plugins/global.lua#L6-L13

This plugin is simple enough and AI will help you very well when you need.

[davinosuke]

No, I do not think it is a bug or anything. I just wanted to know first if there was some configuration or workaround that I was unaware of.

Since that does not seem to be the case, I would like to make this a feature request to extend the plugin. In addition to toggling the IM state, I would like it to be able to run general functions, making changing other settings possible.

Something like this, maybe...

    require("im_select").setup({

        default_im_select  = "keyboard",
        default_command = "fcitx5-remote",

        on_enter_callback = function()
            vim.o.updatetime = 1000000,
        end,

        on_exit_callback = function()
            vim.o.updatetime = 20000;
        end,

    })

If such a thing is possible, of course.
Thank you for your consideration.

[keaising]

No, I do not think it is a bug or anything. I just wanted to know first if there was some configuration or workaround that I was unaware of.

Since that does not seem to be the case, I would like to make this a feature request to extend the plugin. In addition to toggling the IM state, I would like it to be able to run general functions, making changing other settings possible.

Something like this, maybe...

    require("im_select").setup({

        default_im_select  = "keyboard",
        default_command = "fcitx5-remote",

        on_enter_callback = function()
            vim.o.updatetime = 1000000,
        end,

        on_exit_callback = function()
            vim.o.updatetime = 20000;
        end,

    })

If such a thing is possible, of course. Thank you for your consideration.

For now, there is no such callback in this plugin and I don't want to add such callback.

I think you can fork a repo and add vim.o.updatetime = 20000; in these two functions:

im-select.nvim/lua/im_select.lua

Lines 170 to 186 in 113a690

	local function restore_default_im()
	local current = get_current_select(C.default_command)
	vim.api.nvim_set_var("im_select_saved_state", current)
	if current ~= C.default_method_selected then
	change_im_select(C.default_command, C.default_method_selected)
	end
	end
	local function restore_previous_im()
	local current = get_current_select(C.default_command)
	local saved = vim.g["im_select_saved_state"]
	if current ~= saved then
	change_im_select(C.default_command, saved)
	end
	end