Last Call for v0.2

5 views
Skip to first unread message

Keith Dahlby

unread,
Jul 25, 2010, 11:05:26 PM7/25/10
to posh...@googlegroups.com
I finally got around to fixing some bugs that have been annoying me...
  • Special branch status (like my-branch|REBASE-i) actually works now.
  • Merge-conflicted files will no longer show up twice in tab completion lists.
  • Existing variables named $r, $b or $c were accidentally injected into the prompt; Get-GitBranch now clears them in its scope first.
  • Tab expansion is now a lot more flexible in when it will complete, ignoring extra command switches when possible. For example, git add -p <tab> will complete from Working correctly.
Please update to latest when possible and let me know if you find any other glaring issues. I'm thinking of tagging v0.2 soon as the final version that will support msysgit 1.6. Then we can take a dependency on git status -s to improve performance on larger repositories. Thoughts?

Cheers ~
Keith

Jeremy Skinner

unread,
Jul 26, 2010, 3:21:36 AM7/26/10
to posh...@googlegroups.com
Looks good - I like the tab expansion enhancements. 

+1 for making this the last version to support 1.6. I had to revert back to my custom Get-GitStatus as it's still too slow on 1.7.0.2. I also checked with the 1.7.1 beta and it has the same issue.

Git status also has a "-b" flag as of 1.7.1 which shows the branch name when using "status -s", which means if we do switch to this approach then we don't need an additional call to get the current branch.

Jeremy

Jeremy Skinner

unread,
Jul 26, 2010, 3:32:27 AM7/26/10
to posh...@googlegroups.com
For anyone interested, here's a new version of Get-GitStatus that makes use of git 1.7.1's "git status -s -b":

Keith Dahlby

unread,
Jul 26, 2010, 6:14:49 AM7/26/10
to posh...@googlegroups.com
Might want to use git status --porcelain instead, though not sure if it supports -b.

Jeremy Skinner

unread,
Jul 26, 2010, 6:52:34 AM7/26/10
to posh...@googlegroups.com
No, it doesn't seem to support -b when using --porcelain. 

Keith Dahlby

unread,
Jul 26, 2010, 7:04:21 AM7/26/10
to posh...@googlegroups.com
Does git status -z -b work? Can't believe they wouldn't think someone parsing status output might have a use for the branch information.

Jeremy Skinner

unread,
Jul 26, 2010, 7:09:44 AM7/26/10
to posh...@googlegroups.com
git status -z -b seems to just have the same output as a normal git status. However, git status --porcelain -z -b uses NUL line terminators but still doesn't show the branch output. IMO git status -s -b is still the easiest to parse.

Keith Dahlby

unread,
Aug 28, 2010, 1:27:27 PM8/28/10
to posh-git
Only took a month to actually tag the v0.2 release...

http://solutionizing.net/2010/08/28/posh-git-release-v0-2/

Onward to 0.3!

Cheers ~
Keith

On Jul 25, 10:05 pm, Keith Dahlby <dahl...@gmail.com> wrote:
> I finally got around to fixing some bugs that have been annoying me...
>
>    - Special branch status (like my-branch|REBASE-i) actually works now.
>    - Merge-conflicted files will no longer show up twice in tab completion
>    lists.
>    - Existing variables named $r, $b or $c were accidentally injected into
>    the prompt; Get-GitBranch now clears them in its scope first.
>    - Tab expansion is now a lot more flexible in when it will complete,
Reply all
Reply to author
Forward
0 new messages