Fix #85 #65 : Make motion inclusive by default, with support for toggling

[myarcana]

:help forced-motion

I think it would be much more intuitive if hop motions were truly inclusive by default

They were already trying to be, but as #85 points out, it didn't work consistently

I've fixed the behaviour so that hop is always inclusive by default and always consistent, and just like most vim motions, I've also added support to toggle it to be exclusive by pressing v first in operator pending mode (before starting the hop motion, :help o_v)

With this small change, #85's author's snippet

require("hop").setup {}

vim.keymap.set({ "n", "v", "o" }, "f", function()
  vim.cmd "HopChar1CurrentLine"
end, { silent = true })

-- somefn(arg);

Does work exactly the same as the builtin f, try df), df;, dvf;

And if using HopChar1 instead of CurrentLine, then dVf... and d<C-v>f... also behave as you would expect according to all standard vim motions and :help forced-motion.

[myarcana]

I've merged #99 into this, because they don't automatically merge, and they're both solving the same kinds of problem. It makes sense to fix all operator pending behaviour of hop.nvim at the same time.