John J. Foerch writes:

 > The problem you are seeing is an old one.  Conkeror has a command-line
 > component that receives and handles the (possibly remoted) command-line.
 > XULRunner on OS X seems never to call this handler.

I explored this a bit and concluded that there is hope for a solution.

First, Firefox itself behaves exactly the same. If you start the
executable from a shell, you can only run it once. This actually makes
sense for a packaged application under MacOS. Normal double-clicking
from the Finder will never start a second copy of a running
application, so why allow it? You can't pass arguments that way
anyway.

The way MacOS opens links using a browser uses a completely different
mechanism, and the good news is that this also works for Conkeror.
Once you start

     /Applications/Firefox.app/Contents/MacOS/firefox -app /path/to/conkeror

you can use

    open -a Firefox http://some.where.org/

to open another URL. For the moment I use a shell script that checks
if there's a Firefox process and if not starts Conkeror. Then it uses
open to pass in any arguments. This works fine, but it means I can't
use Firefox in parallel with Conkeror.

When I find some time I will try to make a "virtual" application
bundle for Conkeror that gives it its own identity inside MacOS. For
the real executable it soft-link to a Firefox installation. That
should solve all the problems I noted, and even allow to make Conkeror
the default browser under MacOS.

Konrad.
_______________________________________________
Conkeror mailing list
[email protected]
https://www.mozdev.org/mailman/listinfo/conkeror

Reply via email to