Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Can't open new tabs in Firefox from the command line on a Mac

  • 2 përgjigje
  • 1 e ka hasur këtë problem
  • 9 parje
  • Përgjigjja më e re nga cor-el

more options

If I run

   /Applications/Firefox.app/Contents/MacOS/firefox -new-tab https://www.mozilla.org

when Firefox is already running, I get the error "A copy of Firefox is already open. Only one copy of Firefox can be open at a time." It is true that Firefox is already running, but what I am shooting for is getting a new tab in the already running instance, as the -new-tab flag indicates. I get this problem even if the already running instance was started with exactly the same command.

Some of the flags at https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options explicitly say they open new tabs or windows within an existing instance of Firefox, such as -private-window, but I get the same behavior with those flags. What am I doing wrong?

If I run /Applications/Firefox.app/Contents/MacOS/firefox -new-tab https://www.mozilla.org when Firefox is already running, I get the error "A copy of Firefox is already open. Only one copy of Firefox can be open at a time." It is true that Firefox is already running, but what I am shooting for is getting a new tab in the already running instance, as the -new-tab flag indicates. I get this problem even if the already running instance was started with exactly the same command. Some of the flags at https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options explicitly say they open new tabs or windows within an existing instance of Firefox, such as -private-window, but I get the same behavior with those flags. What am I doing wrong?

Krejt Përgjigjet (2)

more options

It appears that as of five years ago this was a known bug with no intended fix: https://bugzilla.mozilla.org/show_bug.cgi?id=393645

more options