Feature: Allow disabling leader key

[alisonjenkins]

The default mapping of the leader key replaces a default mapping of Neovim that I use frequently and I have not found a way to disable the leader key entirely so I can use the proper Neovim Leader key to avoid conflicts with the default Neovim normal mode mappings.

I attempted to set it to null but that results in the default mapping being used and also attempted a empty string but that throws errors.

I am planning to map to my leader (space) followed by a for arrow which is mapped to the arrow open command so this plugin's leader is not required.

[otavioschwanck]

The default mapping of the leader key replaces a default mapping of Neovim that I use frequently and I have not found a way to disable the leader key entirely so I can use the proper Neovim Leader key to avoid conflicts with the default Neovim normal mode mappings.

I attempted to set it to null but that results in the default mapping being used and also attempted a empty string but that throws errors.

I am planning to map to my leader (space) followed by a for arrow which is mapped to the arrow open command so this plugin's leader is not required.

settings the leader from arrow to <leader>a doesn't solve the problem?

[alisonjenkins]

The default mapping of the leader key replaces a default mapping of Neovim that I use frequently and I have not found a way to disable the leader key entirely so I can use the proper Neovim Leader key to avoid conflicts with the default Neovim normal mode mappings.
I attempted to set it to null but that results in the default mapping being used and also attempted a empty string but that throws errors.
I am planning to map to my leader (space) followed by a for arrow which is mapped to the arrow open command so this plugin's leader is not required.

settings the leader from arrow to <leader>a doesn't solve the problem?

No unfortunately, as I don't want the arrow shortcut to just be leader a as I have a nested leader setup where I have mnemonic mappings like for example g goes into my git mappings and ga ultimately resolves in a Git Add.

The built in mapping support should be able to be disabled so we can use the standard mapping features of Neovim to create effects like this and call either the commands that you create or the lua functions directly but as far as I can tell there is no way at current disable the mapping.