about summary refs log tree commit diff
path: root/Functions
Commit message (Collapse)AuthorAgeFilesLines
* 47307: edit-command-line: restrict editing to region if it is activeMikael Magnusson2020-08-161-7/+29
|
* 47306: edit-command-line: add editor styleMikael Magnusson2020-08-161-2/+6
|
* 47305: edit-command-line: when possible, set $BUFFER directlyMikael Magnusson2020-08-161-4/+23
| | | | | | This avoids the send-break which is both visually unappealing and might break some use cases where the user wishes to wrap edit-command-line in another widget.
* 47303: vcs_info hg: Fix changing the expansion of %g (hook_com[guards]) in ↵Daniel Shahaf2020-08-092-4/+10
| | | | | | | | | | | | | | | | | | the set-patch-format hook (regression from workers/40480). To reproduce, go to a hg repository with active mq guards and configure vcs_info as follows: zstyle '*' get-unapplied true zstyle ':vcs_info:*set-patch-format*' hooks f zstyle '*' patch-format '[%g : %G]' zstyle '*' nopatch-format '[%g : %G]' zstyle '*' formats '%m' +vi-f () { hook_com[guards]+=XXX } The regression was first released in 5.3.1-test-2, over three years ago.
* 46072 + 46136: Add the 'zle $widget -f nolast' syntax, to improve ↵Daniel Shahaf2020-06-271-2/+2
| | | | | | add-zle-hook-widget support for multiple hook functions. See workers/46004 for the use-case.
* 46091: Add code to Mercurial VCS backend to show topic if there is any.Manuel Jacob2020-06-221-1/+10
| | | | | | | | "Topics" is an experimental concept in Mercurial that augments the current branching concept (called "named branches"). For more information, see the not always up-to-date Mercurial Wiki page https://www.mercurial-scm.org/wiki/TopicPlan.
* 45644: vcs_info git: Fix current patch's name in several cases.Daniel Shahaf2020-03-281-0/+15
|
* 45627: vcs_info git: Under git-am(1) conflicts, pass to the ↵Daniel Shahaf2020-03-271-3/+11
| | | | | | | | | | | | | | | | | | gen-applied-string hook information on already-applied patches. The hook already receives information about the current (topmost applied) patch and, if the get-unapplied style is set, about future (unapplied) patches. Tested in the Functions/VCS_Info/test-repo-git-rebase-apply scenario, after manually converting the rebase to a «git am». (Specifically, I ran: mkdir d git rebase --abort git format-patch rebase_from_this..HEAD -o d git checkout rebase_onto_this git am d/* .)
* 45625: vcs_info svn: Detect the "working copy format is too new" error.Daniel Shahaf2020-03-271-1/+9
|
* 45626: vcs_info: Deduplicate calling the set-branch-format hook.Daniel Shahaf2020-03-276-33/+31
|
* 45624: vcs_info: Set $rrn in all backends.Daniel Shahaf2020-03-273-0/+4
|
* 45541: internal: vcs_info git: Add a test case repository for rebase-apply ↵Daniel Shahaf2020-03-151-0/+49
| | | | situations
* 45539: vcs_info git: In non-interactive rebases, obtain applied patches' names.Daniel Shahaf2020-03-151-5/+17
|
* 45540: vcs_info git: In non-interactive rebases, compute patch names for ↵Daniel Shahaf2020-03-151-6/+25
| | | | unapplied patches.
* 45543: vcs_info quilt: Allow quiltcommand to be a function.Daniel Shahaf2020-03-151-2/+3
| | | | Before this commit, it could only be an external command.
* 45547: vcs_info git: In interactive rebases, process gen-unapplied-string ↵Daniel Shahaf2020-03-151-7/+16
| | | | | | | arguments like gen-applied-string arguments are processed. I consider this a bugfix, since it's unexpected for -applied and -unapplied to differ about this.
* 45546: vcs_info git: In interactive rebases, properly support the full form ↵Daniel Shahaf2020-03-151-2/+2
| | | | | | | | | | of the "exec" verb. The code before this commit happened to have done the right thing: "exec" lines were handled by the catchall forward compatibility case, which happened to have had virtually the same effect as the correct case. However, that was merely an accidental result. This patch makes the code do the right thing deliberately, rather than by accident.
* 45545: vcs_info git: In interactive rebases, ignore comment lines.Daniel Shahaf2020-03-151-0/+4
|
* github #48/0002: vcs_info git: properly detect bare repositoriesbrian m. carlson2020-02-171-0/+4
| | | | | | | | | | | We currently detect Git repositories by finding the top level of the working tree, and if we fail to detect it, assume that we're not in a repository. However, there's a case we don't consider: a bare repository. Let's detect if the user is in a bare repository by checking if gitdir is set, and if so, using that if there is no working tree. We now detect bare Git repositories with vcs_info, as expected.
* github #48/0001: vcs_info git: avoid warnings in bare repositoriesbrian m. carlson2020-02-171-1/+1
| | | | | | | | | | | | Git 2.25 introduced a change to how git rev-parse --show-toplevel behaves. Traditionally, it succeeded with no output if the user was in a bare repository. Now it dies, printing an error to standard error. Consequently, when the user is in a bare repository with a newer Git, vcs_info prints noisily to standard error. While this is functionally harmless, it is annoying for the shell to print messages from Git every time the prompt is printed, so let's silence the error message.
* 45269: Fix misspellings in completions and elsewhere.Jens Schleusener2020-01-091-1/+1
|
* 45239: Remove 'appendhistory' from zsh-newuser-installAndrey Butirsky2020-01-051-1/+0
| | | | It is on by default, and new users are unlikely to want to change it.
* 45114: vcs_info quilt: Improve support for svn-style patch headers.Daniel Shahaf2019-12-221-7/+13
| | | | | | | | | | Additional lines between the |-separated header line and the actual log message, as generated by 'svn log -v' and 'svn log -g', are now supported. This change affects you if you have quilt patches with 'svn log'-style information in their headers, regardless of whether you use quilt standalone, quilt over svn, or quilt over some other VCS.
* 45003: Fix more documentation typosMartijn Dekker2019-12-112-3/+3
|
* 44960: vcs_info cvs: Fix infinite loop when /CVS exists.Daniel Shahaf2019-12-031-3/+9
|
* 44961: vcs_info svn: Fix infinite loop when /.svn exists.Daniel Shahaf2019-12-031-5/+7
|
* 44962: vcs_info: Document internal function and variableDaniel Shahaf2019-12-032-0/+18
|
* 44958: vcs_info quilt: Avoid forksDaniel Shahaf2019-11-291-5/+5
|
* 44945: vcs_info git: Optimize detection by running fewer external commands.Daniel Shahaf2019-11-291-2/+1
|
* unposted (see 44772): quote the string argument to zle -UBart Schaefer2019-09-241-2/+2
|
* 44305: Fix zsh_directory_name_genericPeter Stephenson2019-07-101-8/+15
| | | | | Longest prefix matching was broken if there were suffixes indicating further handling.
* 43755: Fix state management for repeat uses to avoid clobbering command line ↵Bart Schaefer2019-07-081-2/+3
| | | | when NOT a repeat
* 44020: VCS_INFO_detect_p4: Fix infinite recursiondana2019-01-271-1/+0
|
* unposted, c.f. 43913: emulate -L zsh in edit-command-linePeter Stephenson2018-12-191-0/+2
| | | | Otherwise bad effects observed with GLOB_SUBST set.
* 43879: vcs_info git: Fix fatal error in VCS_INFO_git_getbranch in corner caseDaniel Shahaf2018-12-131-4/+6
| | | | | | | | | | | | | Before this commit, the following use-case: git checkout foo^ git show foo | git am would result in a fatal error, with vcs_info_msg_N_ not set: VCS_INFO_git_getbranch:18: no such file or directory: .git/rebase-apply/onto Now they are set correctly, and HEAD's commit hash is used.
* 43779 (tweaked): add parentheses to fix expression with cprecedences option setJoey Pabalinas2018-11-081-2/+2
|
* 43685: add-zle-hook-widget: Support running under NO_UNSET ('set -u').Daniel Shahaf2018-10-141-6/+6
|
* 43620 (tweaked): vcs_info git: Reverse the order patches are passed to ↵Daniel Shahaf2018-10-082-1/+4
| | | | | | | | gen-unapplied-string in. This is an incompatible change; see README for details. Tweaks (relative to posted version): tweaked README, removed scalpel (debug print).
* 43617: vcs_info git: During a non-interactive rebase of a detached head, ↵Daniel Shahaf2018-10-081-1/+1
| | | | | | | | | | | | | computer the %b expando correctly. Before this commit, the value of %b was the hash of the commit from the "source" side of the rebase, from .git/rebase-apply/orig-head and .git/rebase-apply/original-commit. This broke the invariant that %b expands to a git-rev-parse(1) expression resolving to what %r expands to. Use .git/rebase-apply/onto instead as, empirically, it contains the correct value.
* 43619: vcs_info git: In non-interactive rebases, always set ↵Daniel Shahaf2018-10-081-10/+3
| | | | $hook_com[git_patches_applied] to a string of the form 'foo bar', never just 'foo'.
* 43618: vcs_info: Don't redefine helper functions on every execution of the ↵Daniel Shahaf2018-10-084-2/+13
| | | | | | | autoloadable outer function. This allows enabling tracing of the helper functions without fned'ing the outer function.
* 43587: vcs_info git: In 'git rebase -i', when computing subjects of ↵Daniel Shahaf2018-10-071-0/+19
| | | | applied-patches, handle an edge case where the subject is not available.
* 43588: vcs_info git: Make sure applied-patches is of the form "$hash ↵Daniel Shahaf2018-10-071-0/+5
| | | | | | | | | | | | $subject" --- that is, has a space and a non-empty second argument --- even with future 'git rebase -i' verbs. Use of '?' is consistent with these precedents: Backends/VCS_INFO_get_data_git:220: printf -v "git_patches_applied[$p]" "%04d ?" "$p" Backends/VCS_INFO_get_data_git:242: git_patches_applied+=("? $subject") Backends/VCS_INFO_get_data_git:244: git_patches_applied+=("?") VCS_INFO_quilt:160: applied[$i]+=" ?" VCS_INFO_quilt:168: unapplied[$i]+=" ?"
* 43586: vcs_info git: Reformat to minimise next diff. No functional change.Daniel Shahaf2018-10-071-2/+13
|
* 43585: vcs_info svn: Recognize working copies in need of an upgrade.Daniel Shahaf2018-10-071-1/+10
|
* unposted: Indicate which use-case each branch handles.Daniel Shahaf2018-10-021-1/+3
|
* 43313 (log message tweaked): vcs_info git: For the branch name, try to find ↵Daniel Shahaf2018-08-241-0/+4
| | | | | | | | | | | | a symbolic name before falling back to a raw commit hash. Ask git-describe(1) and git-name-rev(1) to compute a gitrevisions(7) name in terms of a branch or tag that contains (= is a descendant of, is younger than) HEAD. In this repository, the output changes from "9567bfe..." to "master~1" or "remotes/origin/HEAD~1". This would also happen during bisects, e.g., "bisect/bad~22".
* 43314: vcs_info git: Flatten a nested if.Daniel Shahaf2018-08-241-9/+4
| | | | No functional change.
* 43084: Variable warning suppression enhancements.Peter Stephenson2018-06-251-3/+2
| | | | | | Add vared -g option along the lines of typeset -g. Set reply safely in zsh_directory_name_cdr.
* 43030: Replace VCS_INFO_realpath() by :Pdana2018-06-167-20/+11
|
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-11-15 09:10:05 +0000