magit-find-file: Add an option to adjust default branch #3967
Comments
It wasn't my intention for this command to be used like this. I think you should use regular The plan is to remove Once that has been implemented This command will likely be named Considering that (a) I am intending to completely change how this works and (b) you are using the current implementation in an unintended way, I do not want to make the suggested changes. |
|
OK, thanks. I think point (a) is sufficient to decline implementing this, I'm not gonna insist. I'll keep an eye on #2958 . Thanks again for your work! |
counsel-git find a file in the current git repository. "gff" has been occupied by 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. (Ideally magit-find-file should be bound to gfF, since it would be less frequently used than counsel-git; but it is likely too late at this moment.)
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.
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.
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.
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.
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.
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.
Currently, interactively invoking
magit-find-filepops up a list of branches (I'm usingivy), and defaults to the current branch. However, I would prefer{worktree}, which is my most commonly used option. It would be nice ifmagit-find-fileprovides some option to adjust this default option.The text was updated successfully, but these errors were encountered: