Port other completions from git-sh about shgit HOT 3 OPEN

The groundwork's been done. The current design for that functionality is as follows:

1. Aliases and completions are noted in $_git_cmd_cfg.
2. Completion styles may differ, currently shgit knows only stdcmpl.
3. In case of stdcmpl, shgit looks in the completions folder for a completion file with the corresponding command name.

Also, it's all bog-standard bash completion. Granted, that has a bit of a learning curve, but comes naturally once one gets the hang of it.

I'm gradually adding completions, PR's are welcome as well.

As for porting, one can extract a lot of the completions from git-sh's git-completion.bash.
Caveats for this:

1. Some completions are intertwined with various other functions
2. Some completions trigger a lot of I/O and repo-accesses, slowing everything down

My philosophy for adding completions is make to as useful as possible for the user; some commands have tons and tons of flags. Hence, I don't require completions to be exhaustive.

from shgit.

Autocompletion for branch names and remote names would be most important for me, these should also work for the aliased commands. Having the most important flags available helps too. The way I understand it, I/O is triggered only when TAB is pressed?

How important is it to split the completions into separate files? Having everything in one script has its advantages -- installation is much simpler. Perhaps we can still develop in separate files but provide a "builder" script that composes everything into a single (version-controlled) file at development time?

from shgit.

Autocompletion for branch names and remote names would be most important for me, these should also work for the aliased commands. Having the most important flags available helps too. The way I understand it, I/O is triggered only when TAB is pressed?

Aliased commands are now being completed as well.

For non-standard commands, shgit cannot know to complete them further, this can only decided by the alias' author. I aim to add useful completions for the standard ones.

How important is it to split the completions into separate files? Having everything in one script has its advantages -- installation is much simpler.

Quite important, it makes maintaining the code much simpler, and much easier for users to customize. As for installing, I aim to follow the same route as popularized by homebrew; the installation will only be symlinked (so updating/downgrading will be simply done through git).

Perhaps we can still develop in separate files but provide a "builder" script that composes everything into a single (version-controlled) file at development time?

Sure, that could be done, bit esoteric, but I'm not opposed. Would need to handle that in a different issue though.

Branch & remote names will be added next.

from shgit.