-P ProfileName & --profile /path/profile not working Topic is solved

[Lew Rockwell Fan]

I can't get Pale Moon to start directly (as opposed to through the profile manager gui dialog) with any profile but the default.

From "palemoon --help":

Pale Moon options
-P <profile> Start with <profile>.
--profile <path> Start with profile at <path>.
--ProfileManager Start with ProfileManager.

But all 3 of those do pretty much the same thing. If PM is already running they open another tab or window in the same profile. If not, they open the profile manager.

I've also tried lower case -p, --profile='/path/to/profile', changing browser.link.open_newwindow to 2, and adding most possible permutations of --new-instance, --no-remote, & -new-window.

What am I doing wrong?

------
Ubuntu 16.04 built from mini.iso with X, lightdm, and plain Openbox, no DE. amd64. Pale Moon 27.8.1 (64-bit).

[Walter Dnes]

I can't get Pale Moon to start directly (as opposed to through the profile manager gui dialog) with any profile but the default.

From "palemoon --help":

Pale Moon options
-P <profile> Start with <profile>.
--profile <path> Start with profile at <path>.
--ProfileManager Start with ProfileManager.

I know this is going to sound "picky picky picky", but forcing a specific profile has to be done in conjunction with either "-no-remote" or "-new-instance". Those 2 are equivalant, you can use either/or. Here are some snippets from my ICEWM menu...

/home/waltdnes/pm/palemoon/palemoon -new-instance -p dslr
/home/waltdnes/pm/palemoon/palemoon -new-instance -p graphs
/home/waltdnes/pm/palemoon/palemoon -new-instance -p palemoon
/home/waltdnes/pm/palemoon/palemoon -new-instance -p slashdot
/home/waltdnes/pm/palemoon/palemoon -new-instance -p youtube

As mentioned previously, you can use "-no-remote" in place of "-new-instance". Output from "palemoon --help" mentions this.

[Lew Rockwell Fan]

Thanks. In trying to figure why yours worked & mine didn't . . . oh, tell the truth and shame the devil, I was focused so on the command syntax, I hadn't noticed I'd used a lower case letter that should have been a capital in the name of the profile. I'm an idiot sometimes.

It's the kind of goof I'd expect to elicit an error message like "No such profile - starting profile manager" or at least "bad argument" in a terminal, but there was none. Which is why I assumed I'd misunderstood the syntax.