-
Notifications
You must be signed in to change notification settings - Fork 191
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
When using gs
shortcut, the fallback standard git status
is always used
#290
Comments
Maybe this is because of RVM? I'm running
And I cannot reproduce this issue. |
I got the same after installing ruby. $ gs
UPDATE: $ gs
|
Ok, so this is clearly a Windows only issue which is why I wasn't able to reproduce. Something to do with removing the pipe redirection in that raw commandline string gauging from the suggested fix. |
Yes, the fix worked for me as well. Is there a way for some implementation of the fix to be included in the code for Windows users? |
I have the same issue, but using Ubuntu. The windows fix doesn't do anything. |
@ksamuel can you copy the output of you ubuntu systems ruby version?
Something like
```
$ which ruby && ruby --version
```
…On Tue, May 4, 2021, 8:51 AM ksamuel ***@***.***> wrote:
I have the same issue, but using Ubuntu. The windows fix doesn't do
anything.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#290 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABHEKXF33MXBMBTHWRG2ZTTL73UZANCNFSM4HN6NXEA>
.
|
|
Hello, I'm now having to use Ruby and I noticed my previous ticket #242 solution was to uninstall Ruby. I am re-opening this issue for the ruby 2.6.3p62 version compatibility.
I also read the comment in #242 at the end, so I will try it now as well in hopes that it might be as simple as it looks.
The following is the current issue:
Whenever I attempt to run
gs
in bash, I always receive the following message, even though the amount of files changed is far less than 150 changed files. I have tested this on multiple repos. The first repo has 17 file changes. The second repo has 10 file changes."There were more than 150 changed files. SCM Breeze has fallen back to standard
git status
for performance reasons."The text was updated successfully, but these errors were encountered: