| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Based on a patch by Daniel Hahler <git@thequod.de>.
|
| |
|
|
|
|
|
| |
This restores the message when completing a commit object name that
isn't one of the most recent 20 commits. e.g., 'git checkout deadbeef<TAB>'.
|
|
|
|
| |
--fixup' hash completions
|
| |
|
| |
|
|
|
|
|
| |
"git stash" should complete arguments for "git stash save", but without
the message part.
|
|
|
|
|
|
| |
I am not sure about the deprecation of user-commands, but from other
places in the doc and commit history this deprecation was meant to be
reverted?!
|
| |
|
|
|
|
|
|
| |
- 'git rebase': complete arguments in the same word as the option
- 'git commit': provide message for --fixup/--squash
|
|
|
|
|
| |
As the description of that argument says, it's used to *not* perform
sanity checks.
|
|
|
|
|
|
|
|
|
|
|
| |
It is now possible to use the tag-order style to stagger the overwhelming
'git <TAB>' subcommand listing. For example:
zstyle ':completion::complete:git:argument-1:' tag-order \
main-porcelain-commands user-commands third-party-commands \
ancillary-manipulator-commands ancillary-interrogator-commands \
plumbing-manipulator-commands plumbing-interrogator-commands \
aliases
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This incorporates changes mentioned in the release notes since 2.0.0.
|
| |
|
|
|
|
| |
This incorporates changes mentioned in the release notes since 1.9.0.
|
| |
|
|
|
|
|
| |
The git completion for aliases (i.e. completing with aliased verb)
was broken whem some \n exist in aliases.
|
| |
|
|
|
|
|
|
|
|
| |
Src/Zle/compresult.c, Src/Zle/zle_misc.c, Src/Zle/zle_refresh.c: fix
auto-removable suffix highlighting
Completion/Unix/Command/_git: fix compadd for auto-removable suffix in
_git_commit_ranges and _git_stash
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- cherry-pick: allow commit ranges to be specified
- push: option is called --set-upstream and not --set-upstream-to
- status: offer -b,--branch when --porcelain or -z are given
--porcelain and -z don't show the branch info by default, so it
is needed to offer --branch for those options, too.
- checkout: add '--detach' option
- checkout: offer '-l' option when '--orphan' was given
- show-ref: update wording of --head and --heads according to man-page
- config: update default value for color.ui
color-bool was changed to accept a default value as $parts[5]
- add support for 'cygstart' as a valid builtin browser on cygwin
- rebase: add suuport for --autostash and config.autostash
- update builtin browser list
- grep: add --{no,}textconv
- check-ignore: add --no-index
- update-ref: add --stdin -z
- add -C
- pull: add support for --rebase=preserve
- config: add support for http.*. options
- blame: -L can be given multiple times
- config: add support for http.savecookies
- push: add support for --force-with-lease
- diff: --diff-filter: allow lower-case variants (all-but ... specs)
- config: add support for 'fetch.prune' and 'remote.*.prune'
- check-ignore: -z: update message, check-attr: add -z
- config: add diff.orderfile
- revision options: add --exclude
- revision options: add --ignore-missing
- revision options: add --bisect
- rev-parse: add --stuck-long
- merge-base: add --fork-point
- config: implement submodule.*.update completion
- send-email: add --smtp-ssl-cert-path and config options
|
|
|
|
|
|
|
|
|
|
|
|
| |
The output of 'submodule status' is
Xsha1 name (describe)
X being one of -,+,U,[space]
We are only interested in the name part and not the whole line.
Fix the parameter expansions accordingly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this, there were several cases where the completion
would offer the wrong things:
$ git diff branch -- <tab>
would try to complete "changed in workdir files", but needs to
complete all "tree files in HEAD".
$ git diff --cached -- file1 file2 <tab>
would try to complete "changed in workdir files" but needs to
complete "changed in index files".
...
After this change all possible combinations are taken into
account and completion should work properly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
__git_is_committish_range
- Ranges with 3 dots would always fail, because the non-greedy
expansion %..(.|)* in __git_committish_range_first would only
remove '..' and never three dots. 'a...b' would end up in 'a.'.
Use ${${1%..*}%.} instead.
- Use a similar approach for __git_committish_range_last.
- Wrap them in another expansion to replace empty results with 'HEAD'.
Git man-page states omitted range ending are being replaced with
HEAD. This rule has to be followed to make completions like
'git log foo.. -- <tab>' work properly.
- Add an additional check to make sure none of the extracted first/last
parts contain additional '..' in invalied ranges such as 'a..b..c'.
This gets rid of the 'TODO:' and ideally saves a few unneded
calls to git rev-parse.
|
|
|
|
| |
removed by 31159
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Shell functions are strictly ASCII for maximum portability.
Other files within the distribution may contain UTF-8 characters.
Exception for test files: where they need single character input
with the top bit set, ISO-8859-X is used (X doesn't matter as
we don't need the Euro).
|
|
|
|
|
| |
Also reword the explanation slightly to make it more compact since more
explanation is needed.
|
|
|
|
| |
Add _git-check-ignore() and _git-check-mailmap()
|
| |
|
| |
|
| |
|
|
|
|
|
| |
- Add -i and --interactive to _git-clean()
- Add column.clean configuration variable
|
| |
|
|
|
|
|
|
|
| |
commit: '--null' is documented
relink: '-h,--help' are never documented for subcommands but always exist
verify-tag: '-v,--verbose' are documented with updated description
diff: '--cumulative' is deprecated -> remove
|
| |
|
| |
|
|
|
|
| |
The proper syntax is git blame [<commit>] <file> where <commit> is optional.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
While limiting the completion to __git_changed-in-index_files
makes perfect sense for "git diff", it is wrong to use for
"git rm", because it prevents it from completing files present in
HEAD. Giving --cached to git rm is supposed to
"just remove it from the index, keep the working tree copy"
and is in no way related to the file needing to be
modified in the index in the first place.
|