objective: open a url in a specific process from the command-line.
problem: depending on the command-line options, the url is either opened in the wrong process or the attempt fails with an error message.
Steps to Reproduce:
create two profiles p1 and p2
Test 1
launch two instances using different profiles:
Code: Select all
palemoon -P p1 -new-instance
palemoon -P p2 -new-instance
Code: Select all
palemoon -P p1 -new-tab <url>
palemoon -P p2 -new-tab <url>
Two processes are launched by the first set of commands (correct behaviour).
Further urls are always opened in the process which was launched first (in this case p1). The profile parameter is ignored.
Test 2
launch one instance using a specific profile:
Code: Select all
palemoon -P p1 -no-remote
Code: Select all
palemoon -P p1 -new-tab <url>
palemoon -P p1 -remote "openurl(<url>,new-tab)"
Connecting to a process previously launched with -no-remote always fails:
- Opening the second url using -new-tab produces error: "Pale Moon is already running, but is not responding. To open a new window, you must first close the existing Pale Moon process, or restart your system."
- Opening the second url using -remote produces error: "Error: No running window found"
Test 3
launch one instance using a specific profile:
Code: Select all
palemoon -P p1 -new-instance
Code: Select all
palemoon -P p1 -remote "openurl(<url>,new-tab)"
Opening the second url using -remote always produces this error regardless with which parameters the process was originally launched: "Error: No running window found"