bug: mini.jump `t` doesn't work if the following key comes too late when using with noice.nvim
Did you check docs and existing issues?
- [X] I have read all the noice.nvim docs
- [X] I have searched the existing issues of noice.nvim
- [X] I have searched the existing issues of plugins related to this issue
Neovim version (nvim -v)
v0.10.0
Operating system/version
macOS 14.5
Describe the bug
Since I had issues with clever-f (#824), I tried https://github.com/echasnovski/mini.jump, and I noticed that if I e.g. dt, then wait for one second or two, and then hit another key, it does nothing.
Steps To Reproduce
nvim -u repro.lua repro.lua- Hit
dt - Wait for a second or two (Without noice.nvim, it shows
(mini.jump) Enter target single character _in cmd area. This might be relevant?) - Hit another key
Expected Behavior
It deletes contents until the character given by the third key.
Repro
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")
-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end
-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)
-- install plugins
local plugins = {
"folke/tokyonight.nvim",
"MunifTanjim/nui.nvim",
"folke/noice.nvim",
-- "rhysd/clever-f.vim",
"echasnovski/mini.jump",
-- add any other plugins here
}
require("lazy").setup(plugins, {
root = root .. "/plugins",
})
vim.cmd.colorscheme("tokyonight")
-- add anything else here
require("noice").setup({
lsp = {
-- override markdown rendering so that **cmp** and other plugins use **Treesitter**
override = {
["vim.lsp.util.convert_input_to_markdown_lines"] = true,
["vim.lsp.util.stylize_markdown"] = true,
["cmp.entry.get_documentation"] = true, -- requires hrsh7th/nvim-cmp
},
},
-- you can enable a preset for easier configuration
presets = {
bottom_search = true, -- use a classic bottom cmdline for search
command_palette = true, -- position the cmdline and popupmenu together
long_message_to_split = true, -- long messages will be sent to a split
inc_rename = false, -- enables an input dialog for inc-rename.nvim
lsp_doc_border = false, -- add a border to hover docs and signature help
},
})
require('mini.jump').setup()
I did a bisect and the first bad commit was a0c6203d551242322ac7995b26d4e320140e05b1.
This particular issue was gone after checking out a0c6203d551242322ac7995b26d4e320140e05b1~. There were some minor glitches:
- If I do the
dt-> wait -> another flow key before the first mini view pops up (using the timer from #824'srepro.lua), there won't be any mini views showing at all - If I do the flow after the mini views started popping up, it'll pause the pop-ups, move the existing pop-ups to the left (to accommodate
(mini.jump) Enter target single character _presumably), show(mini.jump) Enter target single character _after I hit the third key and resume - The pop-ups lose highlights during the wait between
dtand the third key
It seems #824 is the same issue, as checking out a0c6203d551242322ac7995b26d4e320140e05b1~ resolved it too.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Just tested again and it was still reproducible.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Just tested again and it was still reproducible. (Sorry for the noise. haven't got the permission to remove labels.)
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Just validated again, still had the issue
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Remove stale.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Remove stale.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Remove stale.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Tested eaed6cc and still could reproduce the issue. Remove stale :)
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Remove stale 🙏 (Tested 0427460)
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Remove stale.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Tested again using noice.nvim 0427460, nui.nvim 8d3bce9, mini.jump 65bf2c5.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.
Oops forgot to bump... Reopen?