Remap gx in mini.operators to gX to preserve URI opening functionality

[krovuxdev]

Contributing guidelines

• I have read CODE_OF_CONDUCT.md

Module(s)

mini.operators

Question

I noticed that gx is mapped by default in Neovim to open URIs or files under the cursor (e.g., with a web browser or file explorer). Since I want to preserve this default behavior for gx, I attempted to remap the mini.operators exchange prefix from gx to gX.

Here’s the configuration I tried:

MiniOperators.setup({
    exchange = {
        prefix = "gX", -- or `gl`
    },
})

However, after setting this up, gx still seems to be affected by mini.operators, preventing the default URI-opening functionality from working. How can I properly remap mini.operators to use gX and ensure gx retains its default behavior in Neovim?

as you can see in this picture:

This prevents me from using gx to open links or files.

[abeldekat]

That's strange.

Your setup is working for me.

Do you have a duplicate setup? I can reproduce having both gx and gX for exchange like so:

require("mini.operators").setup()
require("mini.operators").setup({
  exchange = { prefix = "gX" },
})

EDIT:

The init.lua below is also working:

init.lua

---@diagnostic disable: undefined-global
local function setup_deps(path_to_site)
  local mini_path = path_to_site .. "pack/deps/start/mini.nvim"
  if not vim.uv.fs_stat(mini_path) then
    vim.cmd('echo "Installing `mini.nvim`" | redraw')
    vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/echasnovski/mini.nvim", mini_path })
    vim.cmd("packadd mini.nvim | helptags ALL")
    vim.cmd('echo "Installed `mini.nvim`" | redraw')
  end
  require("mini.deps").setup({ path = { package = path_to_site } })
end
setup_deps(vim.fn.stdpath("data") .. "/site/")

vim.g.mapleader = " "
MiniDeps.now(function() require("mini.operators").setup({ exchange = { prefix = "gX" } }) end)

The output of commands :map gx and :map gX is correct.

[echasnovski]

Yes, everything works here as expected and is probably the result of several setup() calls.

@krovuxdev, the shear fact that you use MiniOperators.setup (instead of require('mini.operators').setup) and it works, means that there was a require('mini.operators').setup() call before it. The MiniOperators global table is created only inside that call. Remove that prior call and use require('mini.operators').setup() here.

---

That said, I'd suggest the other way around and map gX to open URI under cursor (prior to calling require('mini.operators').setup). Here is how I do it. That said, I think this should be done by 'mini.operators' itself (same as it clears up gr* built-in mappings for gr)... 🤔

[krovuxdev]

@abeldekat Thanks for replying.

Yes, because I have the module loading like this:

local mini_modules = {
-- more
"operators"
}
vim.tbl_map(function(module) pcall(require("mini." .. module).setup) end, mini_modules)

MiniOperators.setup({
-- configure
})

I don't understand why others like Pick and Files work without duplicating keymaps.
I guess I'll see what to do. Thank you very much.

the shear fact that you use MiniOperators.setup (instead of require('mini.operators').setup) and it works, means that there was a require('mini.operators').setup() call before it. The MiniOperators global table is created only inside that call. Remove that prior call and use require('mini.operators').setup() here.

I wonder why the other mini modules work using MiniPick.setup, changing keymaps without duplicating anything 🤔. Could you explain why operators behaves differently? (just out of curiosity)

That said, I'd suggest the other way around and map gX to open URI under cursor (prior to calling require('mini.operators').setup). Here is how I do it. That said, I think this should be done by 'mini.operators' itself (same as it clears up gr* built-in mappings for gr)... 🤔

@echasnovski That helped me with your remap code, although I liked it more with MiniOperators.xxx, but unfortunately I have to use remap. Thank you very much.

[echasnovski]

I wonder why the other mini modules work using MiniPick.setup, changing keymaps without duplicating anything 🤔. Could you explain why operators behaves differently? (just out of curiosity)

The 'mini.operators' module, as well as many others (like 'mini.operators', 'mini.surround', 'mini.ai', 'mini.move', 'miin.splitjoin', 'mini.completion', 'mini.diff', etc.) creates global mappings inside its setup() call.

Only some modules don't create global mappings. Instead they create buffer-local (like 'mini.files'), temporary (like jump_next, jump_prev, stop in 'mini.snippets'; but not expand), or not "true" mappings at all (like 'mini.pick').

[krovuxdev]

I wonder why the other mini modules work using MiniPick.setup, changing keymaps without duplicating anything 🤔. Could you explain why operators behaves differently? (just out of curiosity)

The 'mini.operators' module, as well as many others (like 'mini.operators', 'mini.surround', 'mini.ai', 'mini.move', 'miin.splitjoin', 'mini.completion', 'mini.diff', etc.) creates global mappings inside its setup() call.

Only some modules don't create global mappings. Instead they create buffer-local (like 'mini.files'), temporary (like jump_next, jump_prev, stop in 'mini.snippets'; but not expand), or not "true" mappings at all (like 'mini.pick').

I see, thank you very much for explaining :)