From 7ea148a1dc1518bc8a6835c0329894a590135937 Mon Sep 17 00:00:00 2001
From: "Justin M. Keyes" <justinkz@gmail.com>
Date: Wed, 11 Mar 2026 14:25:12 +0100
Subject: docs: use "ev" convention in event-handlers

Problem:
In autocmd examples, using "args" as the event-object name is vague and
may be confused with a user-command.

Solution:
Use "ev" as the conventional event-object name.
---
 runtime/lua/vim/termcap.lua | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'runtime/lua/vim/termcap.lua')

diff --git a/runtime/lua/vim/termcap.lua b/runtime/lua/vim/termcap.lua
index 887fd5b58f..937fee1024 100644
--- a/runtime/lua/vim/termcap.lua
+++ b/runtime/lua/vim/termcap.lua
@@ -33,8 +33,8 @@ function M.query(caps, cb)
 
   local id = vim.api.nvim_create_autocmd('TermResponse', {
     nested = true,
-    callback = function(args)
-      local resp = args.data.sequence ---@type string
+    callback = function(ev)
+      local resp = ev.data.sequence ---@type string
       local k, rest = resp:match('^\027P1%+r(%x+)(.*)$')
       if k and rest then
         local cap = vim.text.hexdecode(k)
-- 
cgit