Replies: 1 comment
-
But that's the exclusive target audience: developers of Git for Windows.
It would be an option, of course. But no Git for Windows developer ever complained, and honestly, I don't think that everybody should be forced to retrain their fingers just because somebody who freely admits not to contribute to Git for Windows is inconvenienced when using Git for Windows' SDK (when they should use regular Git for Windows instead). |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This may be a little of an edge case, so i do not want to make it a issue at all.
For myself i already fixed it locally.
But i wanted to let you know about it, because it may still be worth thinking about it because others may come across the same issue.
I'm a longtime user of sdkman on windows which uses
sdkas a shortcut/alias.And i am somewhat used to have sdk to call sdkman.
I'm kinda new to git-sdk, i'm also not using it for active development of git or such.
I just find it nice to have a extended possibilities by having a full msys install underneath with access to more linux commands/tools than just the plain git-for-windows. Its just like having both worlds git-for-windows and a msys2 install but together without having to change the mintty profile).
Now my issue is/was that git-sdk also uses sdk as a name for a function.
Resulting in CMD, Powershell and even normal git-for-windows mintty still having sdk as the alias for sdkman but in the mintty for git-sdk sdk triggers the sdk function.
Maybe another name would be an option.
Or at least a little section in the install instruction or on the wiki page,
with something like: "Hey if you also have sdkman installed you may want to change either sdkmans alias or the name of the git-sdks sdk function to still have access to both of them"
Beta Was this translation helpful? Give feedback.
All reactions