Groupy ignores WorkingDirectory setting

from Stardock Forums

On up-to-date Win10 x64, I create a group containing an instance of cmd.exe and another of Git Bash. I notice that whenever I launch the group, both start in C:\windows\system32. I locate the group file (included below) and edit the WorkingDirectory setting, but this has no effect, they still both start in C:\windows\system32.

 

[Group]
GroupCount=2
GroupLeft=7
GroupTop=44
GroupRight=1360
GroupBottom=654
GroupMax=0
[GroupyEntry1]
OwnerProcess=C:\Windows\System32\cmd.exe
RunElevated=0
NoPatternMatching=0
CommandLine="/K C:\Users\jacro\py_mlao\Scripts\activate.bat"
WorkingDirectory=C:\Users\jacro\devel\mlao
Target=C:\Windows\System32\cmd.exe
MatchingClass=ConsoleWindowClass
[GroupyEntry2]
OwnerProcess=C:\Program Files\Git\usr\bin\mintty.exe
RunElevated=0
NoPatternMatching=0
CommandLine="--nodaemon -o AppID=GitForWindows.Bash -o AppLaunchCmd="C:\Program Files\Git\git-bash.exe" -o AppName="Git Bash" -i "C:\Program Files\Git\git-bash.exe" --store-taskbar-properties -- /usr/bin/bash --login -i"
WorkingDirectory=C:\Users\jacro\devel\mlao
Target=C:\Program Files\Git\usr\bin\mintty.exe
MatchingClass=mintty

groupy
5,737 views 3 replies
Reply #1 from Stardock Forums Top

Hello,
I have forward your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #2 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.

So this is the edited file, yes? What is the original?

Why would you expect cmd to work from that working directory?

Are any to be run elevated?

What is not happening as a result, what is not working because of any issue you are seeing?

Sean Drohan
Stardock Support Manager

Fences - Organize your desktop icons today!
Reply #3 from Stardock Forums Top

My prior work sequence: I would run "git bash" from the Windows menu & it woud start in my user directory (C:\Users\jacro); this is its default behavior. I would run cmd.exe using a shortcut so that it starts in my project directory, in this case C:\Users\jacro\devel\mlao. I have full access to this directory, because its in my user directory.

I drag one onto the other and save them as a Groupy group. I start the group and note that both shells start in C:\windows\system32. I open the .groupy files in an editor and note that there is a "WorkingDirectory" setting (I *do not* notice that this is already being ignored for Git Bash, see the original file below). I edit this entry, but with no effect.

This makes the "save group" feature of Groupy *less* convenient than just starting the two shells separately as I did before.

I had to re-create the original .groupy file, here it is (only difference from edited version is "WorkingDirectory" lines):

[Group]
GroupCount=2
GroupLeft=7
GroupTop=44
GroupRight=1360
GroupBottom=654
GroupMax=0
[GroupyEntry1]
OwnerProcess=C:\Windows\System32\cmd.exe
RunElevated=0
NoPatternMatching=0
CommandLine="/K C:\Users\jacro\py_mlao\Scripts\activate.bat"
WorkingDirectory=C:\Windows\System32
Target=C:\Windows\System32\cmd.exe
MatchingClass=ConsoleWindowClass
[GroupyEntry2]
OwnerProcess=C:\Program Files\Git\usr\bin\mintty.exe
RunElevated=0
NoPatternMatching=0
CommandLine="--nodaemon -o AppID=GitForWindows.Bash -o AppLaunchCmd="C:\Program Files\Git\git-bash.exe" -o AppName="Git Bash" -i "C:\Program Files\Git\git-bash.exe" --store-taskbar-properties -- /usr/bin/bash --login -i"
WorkingDirectory=C:\Program Files\Git\usr\bin
Target=C:\Program Files\Git\usr\bin\mintty.exe
MatchingClass=mintty