From ac65aa26cb70f152f172a6fa953029fd8fb9a496 Mon Sep 17 00:00:00 2001
From: Sanchayan Maity <sanchayan@sanchayanmaity.net>
Date: Mon, 12 Dec 2022 10:10:00 +0530
Subject: [PATCH] nvim: lsp: Use local leader for running code lens

We use <Leader>l for linting. This should have been done as part of
commit b294f19.
---
 nvim/.config/nvim/lua/lsp.lua | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/nvim/.config/nvim/lua/lsp.lua b/nvim/.config/nvim/lua/lsp.lua
index 3dfb887..39063d8 100644
--- a/nvim/.config/nvim/lua/lsp.lua
+++ b/nvim/.config/nvim/lua/lsp.lua
@@ -156,7 +156,7 @@ local on_attach = function(client, bufnr)
 
   if client.server_capabilities.codeLensProvider or client.server_capabilities.documentHighlightProvider then
     if client.server_capabilities.codeLensProvider then
-      vim.api.nvim_buf_set_keymap(bufnr, "n", "<Leader>l", "<cmd>lua vim.lsp.codelens.run()<CR>", opts)
+      vim.api.nvim_buf_set_keymap(bufnr, "n", "<LocalLeader>l", "<cmd>lua vim.lsp.codelens.run()<CR>", opts)
       vim.api.nvim_create_autocmd({"CursorHold", "CursorHoldI", "InsertLeave"}, {
         group    = lsp_augroup_id,
         buffer   = bufnr,