-
Bug
-
Resolution: Unresolved
-
High
-
None
-
2.4.7.0
-
Windows 10, from PowerShell, opened per command line
-
Severity 2 - Major
I want to open SourceTree per command line in the current repository.
If I run $env:LOCALAPPDATA\SourceTree\SourceTree.exe -f . status then SourceTree opens, but not in the current repository.
If I run $env:LOCALAPPDATA\SourceTree\app-2.4.7\SourceTree.exe -f . status then SourceTree opens correctly with the current repository.
Since this is a Squirrel app, it is not feasible to use the hard path with the version. The Sourcetree start wrapper should route all command line parameters to the actual exe.
Form Name |
---|
[SRCTREEWIN-8307] SourceTree does not honor command line parameters in Windows correctly
Workflow | Original: JAC Bug Workflow v3 [ 3453776 ] | New: SRCTREE JAC Bug Workflow [ 3744273 ] |
Workflow | Original: SourceTree Bug Workflow [ 2506087 ] | New: JAC Bug Workflow v3 [ 3453776 ] |
Status | Original: Verified [ 10005 ] | New: Gathering Impact [ 12072 ] |
Labels | New: installation squirrel |
Status | Original: Open [ 1 ] | New: Verified [ 10005 ] |
Component/s | New: General [ 20292 ] | |
Component/s | Original: General [ 16290 ] | |
Component/s | Original: Windows [ 42393 ] | |
Key | Original: SRCTREE-5281 | New: SRCTREEWIN-8307 |
Affects Version/s | New: 2.4.7.0 [ 77427 ] | |
Affects Version/s | Original: 2.4.7.0 [ 77524 ] | |
Project | Original: SourceTree For Mac [ 12910 ] | New: SourceTree for Windows [ 14510 ] |
Description |
Original:
I want to open SourceTree per command line in the current browser.
If I run {{$env:LOCALAPPDATA\SourceTree\SourceTree.exe -f . status}} then SourceTree opens, but not in the current repository. If I run {{$env:LOCALAPPDATA\SourceTree\app-2.4.7\SourceTree.exe -f . status}} then SourceTree opens correctly with the current repository. Since this is a Squirrel app, it is not feasible to use the hard path with the version. The Sourcetree start wrapper should route all command line parameters to the actual exe. |
New:
I want to open SourceTree per command line in the current repository.
If I run {{$env:LOCALAPPDATA\SourceTree\SourceTree.exe -f . status}} then SourceTree opens, but not in the current repository. If I run {{$env:LOCALAPPDATA\SourceTree\app-2.4.7\SourceTree.exe -f . status}} then SourceTree opens correctly with the current repository. Since this is a Squirrel app, it is not feasible to use the hard path with the version. The Sourcetree start wrapper should route all command line parameters to the actual exe. |
Description |
Original:
I want to open SourceTree per command line in the current browser.
If I run {{C:\Users\mgondermann\AppData\Local\SourceTree\SourceTree.exe -f . status}} then SourceTree opens, but not in the current repository. If I run {{C:\Users\mgondermann\AppData\Local\SourceTree\app-2.4.7\SourceTree.exe -f . status}} then SourceTree opens correctly with the current repository. Since this is a Squirrel app, it is not feasible to use the hard path with the version. The Sourcetree start wrapper should route all command line parameters to the actual exe. |
New:
I want to open SourceTree per command line in the current browser.
If I run {{$env:LOCALAPPDATA\SourceTree\SourceTree.exe -f . status}} then SourceTree opens, but not in the current repository. If I run {{$env:LOCALAPPDATA\SourceTree\app-2.4.7\SourceTree.exe -f . status}} then SourceTree opens correctly with the current repository. Since this is a Squirrel app, it is not feasible to use the hard path with the version. The Sourcetree start wrapper should route all command line parameters to the actual exe. |
I just found a workaround.
It seems, that relative paths are not working (the . especially) because the squirrel wrapper and the updater.exe seem to redirect the current directory to the installation dir.
got it working with
as $PWD returns the absolute path of the current directory