[mini.bracketed] Alternate mappings optimized for bidirectional navigation

[pkazmier]

While I really like the functionality provided by 'mini.bracketed', I struggle with the default mappings. I'm simply unable to quickly execute bindings that start with [ or ], so repeated presses are especially challenging. I'm not sure if this is because I type in Dvorak, which maps the brackets to -/= keys, or my right pinky is just defective, but this is why I like to use 'mini.clues' postkeys for all of my bracketed targets. It greatly simplifies repeated target invocation for me, but it only works when navigating in a single direction. As soon as I want to reverse direction, I need to cancel the current postkeys operation and then reach for the other bracket key to change direction.

This morning while reviewing my 'mini.bracketed' configuration, I realized that I never use the first or last targets bound to the uppercase version of the suffix. So I thought why not remap the uppercase suffix to go in the reverse direction. For example, [D would move forward instead of going to the first. Likewise ]D would move backward instead of going to the last. When combined with postkeys, this lets me very quickly navigate back and forth between targets—especially useful if you overshoot.

I thought I'd share my configuration in case others have the same struggles that I have with the defaults:

later(function() -- mini.bracketed
  require('mini.bracketed').setup() 

  local clues = {}
  for target, opts in pairs(MiniBracketed.config) do
    local lower_suffix = opts.suffix
    local upper_suffix = opts.suffix:upper()
    local replacements = {
      ["["]  = { old = "first", new = "forward" },
      ["]"]  = { old = "last", new = "backward" },
    }

    for bracket, pattern in pairs(replacements) do
      -- Use hydra mode for all bracketed targets
      table.insert(clues, { mode = "n", keys = bracket .. lower_suffix, postkeys = bracket })
      table.insert(clues, { mode = "n", keys = bracket .. upper_suffix, postkeys = bracket })
  
      -- Make uppercase navigate in other direction instead of first/last
      local map = vim.fn.maparg(bracket .. upper_suffix, "n", false, true)
      local new_rhs = map.rhs:gsub(pattern.old, pattern.new)
      local new_desc = map.desc:gsub(pattern.old, pattern.new)
      vim.keymap.set("n", bracket .. upper_suffix, new_rhs, { desc = new_desc })
    end
  end

  -- These will be used later when mini.clues is setup
  _G.Config.bracketed_clues = clues
end)

[pkazmier]

Screenshots showing what the mappings look like afterwards:

[echasnovski]

... but this is why I like to use 'mini.clues' postkeys for all of my bracketed targets. It greatly simplifies repeated target invocation for me, but it only works when navigating in a single direction. As soon as I want to reverse direction, I need to cancel the current postkeys operation and then reach for the other bracket key to change direction.

Yeah, this is the most visible shortcoming of 'mini.clue' approach to "submodes" when it comes to 'mini.bracketed'. But it is what it is: [ / ] keys meaning "previous" and "next" is a fairly established rule at this point.

This morning while reviewing my 'mini.bracketed' configuration, I realized that I never use the first or last targets bound to the uppercase version of the suffix. So I thought why not remap the uppercase suffix to go in the reverse direction.

That does sound interesting and good that it works for you! I personally use "first"/"last" too much to find it comfortable without them. My usual cases are:

• [B / ]B to go to first/last buffer (based on 'mini.tabline'). Combined with [count] to go second/third/n-th first/last is how I usually navigate buffers. The :Pick buffers usually comes if there are more buffers than fits the screen (which is not that often).
• Ensure to go first instance of something in a buffer where regular navigation I prefer to wrap. Like "first diagnostic", "first merge conflict", "first git hunk", etc. Yes, these can be managed with something like gg]d and G[d, but that is not 1005 solution because first/last lines can be part of first/last instance.

[pkazmier]

• [B / ]B to go to first/last buffer (based on 'mini.tabline'). Combined with [count] to go second/third/n-th first/last is how I usually navigate buffers. The :Pick buffers usually comes if there are more buffers than fits the screen (which is not that often).

For switching buffers in the tabline, I still feel that H and L are most intuitive just because of the horizontal orientation of the tabline, so I generally use these bindings:

map("n", "H",         C"lua MiniBracketed.buffer('backward')", "Prev buffer")
map("n", "L",         C"lua MiniBracketed.buffer('forward')",  "Next buffer")

[echasnovski]

Yes, I thought about that too. Turns out I use default H and L a lot during navigation. To each their own, I guess :)