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.
Hello 馃憢
as someone who loves TPM but uses a different key binding for pane navigation, I was a bit annoyed that the provided TPM plugin does not support configuring the key mapping for navigation. Of course, someone could resort to copying the provided setting to their .tmux.conf (or even fork this project), but I believe in using plugins to keep the config clean.
Thus, I've updated the plugin to support parameters for configuring the key mapping. It is possible to have multiple keys for each navigation action, as well as disable an individual mapping if desired. Have a look in the updated README to see how it works.
I've tested my changes in tmux version 3.2a, 3.4, as well as 2.9a (as the configuration parsing had some breaking changes in version 3.0). I hope I didn't miss any weird corner case.