Skip to content

Add copy-mode-vi bindings for search keys#23

Closed
liangkarl wants to merge 2 commits intoddzero2c:masterfrom
liangkarl:master
Closed

Add copy-mode-vi bindings for search keys#23
liangkarl wants to merge 2 commits intoddzero2c:masterfrom
liangkarl:master

Conversation

@liangkarl
Copy link
Copy Markdown
Contributor

There is a use case that the user may jump in copy mode, which didn't have valid operation for this.

@ddzero2c
Copy link
Copy Markdown
Owner

Thanks for the contribution! Just to clarify — since tmux bind registers to the prefix table by default, prefix + s already works in copy mode without any extra configuration.

If you specifically need to trigger easymotion without the prefix key in copy mode, I'd suggest making it opt-in via a config option rather than changing the default, so existing users won't have their copy-mode-vi bindings overwritten unexpectedly. Could you share more about your use case?

@liangkarl
Copy link
Copy Markdown
Contributor Author

Yes, using prefix + s is reasonable when the console isn't in any tmux mode. However, when tmux is already in copy mode, it would be a little weird to enforce using prefix + s. Just like the default keybinds C-d and C-u of copy mode, we use C-d and C-u to do page down and up instead of using prefix + C-d or prefix + C-u. That's the same reason.

About the implementation, it's flexible. As you said, it could be optional. I chose the easy way as I didn't think too much. Please change it to whatever you want.

ddzero2c added a commit that referenced this pull request Mar 26, 2026
Add @easymotion-copy-mode-no-prefix option (default: false) to bind
easymotion keys directly in copy mode without requiring the prefix key.
Automatically detects vi/emacs mode-keys to select the correct key table.

Closes #23
@ddzero2c ddzero2c closed this in #25 Mar 26, 2026
@ddzero2c
Copy link
Copy Markdown
Owner

Related to #24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants