Skip to content

Conversation

chevcast
Copy link

@chevcast chevcast commented Jun 7, 2024

I've added a note to the README showing how to make this work for users using zsh-vi-mode.

Resolves the concerns in issue #23

@chevcast chevcast force-pushed the main branch 3 times, most recently from b3a01bb to eeb89f6 Compare June 7, 2024 16:39
eval "zvm_bindkey visual '^g^${o[1]}' fzf-git-$o-widget"
eval "zvm_bindkey visual '^g${o[1]}' fzf-git-$o-widget"
done
}
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pulled from: #23 (comment)

function zvm_after_init() {
zvm_bindkey viins "^P" up-line-or-beginning-search
zvm_bindkey viins "^N" down-line-or-beginning-search
for o in files branches tags remotes hashes stashes lreflogs each_ref; do
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is missing the recent addition of "worktrees". Whenever we add something, each user will have to update their configuration accordingly not to miss the update. How about providing a function instead so that the users don't have to manually update their code?

# Call _fzf_git_zvm_after_init from your zvm_after_init
function zvm_after_init() {
  _fzf_git_zvm_after_init
}

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