You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fish should seach executable files like: git-command and complete its by tab.
For example, i have: /usr/local/bin/git-history
When i type: git histo<TAB>, it should complete it.
Bash makes it correctly.
The text was updated successfully, but these errors were encountered:
Looks like that picks up all git commands, not just custom commands. Custom commands "git foo" can be completed by completing the name "git-foo" instead, which is all git does to find them anyway.
The benefit of bash's approach is it will pick up new builtin git commands as well, though the downside is it will expose them by default, whereas the current git bash completion actually blacklists a lot of commands (e.g. plumbing commands).
Fish should seach executable files like: git-command and complete its by tab.
For example, i have:
/usr/local/bin/git-history
When i type:
git histo<TAB>
, it should complete it.Bash makes it correctly.
The text was updated successfully, but these errors were encountered: