-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bound counsel-git to gff and move magit-find-file to gfF. #12795
Conversation
If I've found it useful, for example when looking at a I don't think it's to late to swap them. More frequently used commands should require fewer key presses. Opening a file in a branch seems like an alternate behavior, therefore it's probably better to have it under It would also be easier to remember and expect the following behavior.
Could you add entries in It could say something like this:
And rewrite the outdated commit title and message. |
I will make the suggested changes. |
counsel-git find a file in the current git repository. "gff" is currently bound to magit-find-file. While counsel-git seemingly performs the same functionality as magit-find-file, they are substantially different: magit-find-file is not intended to find a file, contrary to what the name indicates. See magit/magit#3967 for explanation. This is why we need another key binding for counsel-git.
@duianto Updated |
Thank you for contributing to Spacemacs. It's safe to delete your branch. Nice catch. Your right the magit-find-file changelog entry goes in the git section. |
I use SPC g f f ( |
@Miciah |
counsel-git find a file in the current git repository. "gff" is
currently bound to magit-find-file. While counsel-git seemingly performs the
same functionality as magit-find-file, they are substantially different:
magit-find-file is not intended to find a file, contrary to what the
name indicates. See magit/magit#3967 for
explanation. This is why we need another key binding for counsel-git.