Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
I noticed this here, and wasn't going to look into it. But I started getting into paredit myself, so I encountered the same issue. Now it's personal..
Issue: feature: the undefine-key function to delete an existing key in a keymap.
Change Description
Add public function:
undefine-keys
and marcoundefine-keys
. These are very much in the same style as theirdefine
counterparts.Testing
I tested both functionality in my own config:
I also tested attempting to undefine keys that don't exist in the map. This is fine with no errors.
For example with paredit, you can define your own keys before or after undefining the paredit keys, as it will just remove from the map, your keys and paredit will not interfere.
You can undefine keys to your hearts content: