fix: make the plugin work even if g@ is remapped

Similar to #2

lua/coerce/conversion.lua

@@ -99,9 +99,10 @@ end
 --@treturn Region The selected region.
 M.select_with_motion = function()
 	local operator_m = require("coerce.operator")
-	-- The "i" mode is important. We might be running within a feedkeys() call, so we need to insert
+	-- The i-mode is important. We might be running within a feedkeys() call, so we need to insert
 	-- the operator into the typeahead buffer immediately before the motion.
-	return operator_m.operator("im", "")
+	-- The n-mode is also important. We don’t want user remaps of g@ to interfere with the operator.
+	return operator_m.operator("in", "")
 end
 
 --- Selects the current visual selection.

tests/coerce/operator_spec.lua

@@ -20,7 +20,7 @@ describe("coerce.operator", function()
 	describe("operator", function()
 		it("returns the selected region", function()
 			test_helpers.create_buf({ "Hello, world!" })
-			local selected_region = co.operator("m", "iw")
+			local selected_region = co.operator("n", "iw")
 
 			assert.are.same({
 				mode = region.modes.CHAR,

tests/coerce_spec.lua

@@ -42,6 +42,19 @@ describe("coerce", function()
 		assert.are.same({ "MY_CASE" }, lines)
 	end)
 
+	it("works with motion selection even with a user-defined g@ keymap", function()
+		local buf = test_helpers.create_buf({ "myCase" })
+		vim.keymap.set("n", "g@", '<cmd>echo "Pressed g@"<cr>')
+		c.setup({})
+		-- `gcr` starts the operator pending mode
+		-- `u` select upper case coercion
+		-- `e` select the keyword
+		test_helpers.execute_keys("gcrue", "x")
+
+		local lines = vim.api.nvim_buf_get_lines(buf, 0, 1, true)
+		assert.are.same({ "MY_CASE" }, lines)
+	end)
+
 	it("displays an error for a multiline selection in visual mode", function()
 		local buf = test_helpers.create_buf({ "myCase", "yourCase" })
 		local notification = nil