"firefox -new-window grooveshark.com" and "start with firefox"

[memeplex]

Say you configured keysharky to start with firefox at port 8800. If you have opened a firefox window and then do firefox -new-window grooveshark.com (notice that the argument is -new-window and not -new-instance) this second window won't be able to listen at 8800. It seems like every window is trying to create a new keysharky server. This is not right, maybe keysharky should do that upon -new-instance but clearly a new window doesn't require a new server.

[memeplex]

The behavior is even more bizarre as if you open grooveshark in the initial window (at port 8800) and then drag it out to create a new window of its own, this new window will still listen at 8800. This behavior seems right to me but it's not consistent with the previously described one.

[intarstudents]

Well, I haven't used keySharky for over maybe two years and when I used, most of time I runned one firefox windows with all tabs in there so I didn't run into this bug, anyway it was programmed for mine one windowzed mode :) because it was tool for me and after that for others to use.

Hmm I don't say I will fix this (maybe there are some new nice ways to do this), but will look into, yes.

[memeplex]

Ok, I understand your situation and thank you for looking into it. As a workaround linux users could use xdotool to send keysharky shortcuts to the grooveshark window (although the method is not very reliable except when you have a dedicated grooveshark window).