marco/mvim
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[keymaps] Remove some comments

Browse Source
This commit is contained in:
MDS
2026-01-03 17:11:42 +01:00
parent 2038eb9f87
commit 96596c2908
1 changed files with 0 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
plugin/20_keymaps.lua
View File

@@ -34,18 +34,6 @@ nmap(']p', '<Cmd>exe "put " . v:register<CR>', 'Paste Below')
-- In 'plugin/10_options.lua' <Leader> is set to <Space>, i.e. press <Space> -- In 'plugin/10_options.lua' <Leader> is set to <Space>, i.e. press <Space>
-- whenever there is a suggestion to press <Leader>. -- whenever there is a suggestion to press <Leader>.
-- --
-- This config uses a "two key Leader mappings" approach: first key describes
-- semantic group, second key executes an action. Both keys are usually chosen
-- to create some kind of mnemonic.
-- Example: `<Leader>f` groups "find" type of actions; `<Leader>ff` - find files.
-- Use this section to add Leader mappings in a structural manner.
--
-- Usually if there are global and local kinds of actions, lowercase second key
-- denotes global and uppercase - local.
-- Example: `<Leader>fs` / `<Leader>fS` - find workspace/document LSP symbols.
--
-- Many of the mappings use 'mini.nvim' modules set up in 'plugin/30_mini.lua'.
-- Create a global table with information about Leader groups in certain modes. -- Create a global table with information about Leader groups in certain modes.
-- This is used to provide 'mini.clue' with extra clues. -- This is used to provide 'mini.clue' with extra clues.
-- Add an entry if you create a new group. -- Add an entry if you create a new group.