Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gs a bit confused in /tmp #31

Closed
hugovk opened this issue Oct 15, 2017 · 2 comments
Closed

gs a bit confused in /tmp #31

hugovk opened this issue Oct 15, 2017 · 2 comments

Comments

@hugovk
Copy link

hugovk commented Oct 15, 2017

scmpuff 0.2.1
git version 2.14.0
macOS Sierra

Clone a repo in /tmp and make a change. First confirm gs is aliased to scmpuff:

[hugo:/tmp/scmpuff] master(+1/-0) ± which gs
gs: aliased to scmpuff_status

Then do a gs:

[hugo:/tmp/scmpuff] master(+1/-0) ± gs
# On branch: master  |  [*] => $e*
#
➤ Changes not staged for commit
#
#       modified:  [1] ../../private/tmp/scmpuff/README.md
#

Compare with a bog standard git status:

[hugo:/tmp/scmpuff] master(+1/-0) ± git status
On branch master
Your branch is up-to-date with 'origin/master'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   README.md

no changes added to commit (use "git add" and/or "git commit -a")
[hugo:/tmp/scmpuff] master(+1/-0) ±

It'd be nice if gs also showed README.md rather than ../../private/tmp/scmpuff/README.md.

@hugovk
Copy link
Author

hugovk commented Oct 15, 2017

Can be reproduced with either of:

/usr/bin/env scmpuff status --filelist
/usr/bin/env scmpuff status

Having a bit of the poke in status.go, the first two Git commands look fine:

[hugo:/tmp/scmpuff] master(+1/-0) ± git status --porcelain
 M README.md
[hugo:/tmp/scmpuff] master(+1/-0) ± git status -z -b
## master...origin/master M README.md%

But perhaps this is the culprit?

[hugo:/tmp/scmpuff] master(+1/-0) 1 ± git rev-parse --show-toplevel
/private/tmp/scmpuff

@mroth
Copy link
Owner

mroth commented Oct 16, 2017

Hi, this is actually an upstream issue with Go itself that we haven't worked around yet, please see #11 for details.

(Closing this one as duplicate, but appreciate the detailed issue report greatly!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants