On Sat, Apr 13, 2002 at 01:39:57PM +0200, Martin Costabel wrote: > There seems to be something else here. I have now played with launch a > bit. Turns out: > > launch http://www.cnn.com opens IE > launch -l http://www.cnn.com opens OmniWeb (set as default browser) > > everytime.
This is why the -l option is there. Launch Services and Internet Config use different mechanisms to look up protocol handlers (even though, according to Apple, Internet Config is just a layer on top of Launch Services in OS X). I've generally found launch -l to be more reliable. In my case, both 'launch' and 'launch -l' open Mozilla, which is set as my current browser. > Opening a file locally always opens IE, irrespective of whether I call > it with "launch" or with "launch -l" and whether I give just the > filename or file://<filename>. Local files aren't resolved by protocol but by extension. So you need to go into the Finder, and select OmniWeb in the "Open with application" pane of the Info window, and click "Change All". You can override Launch Services extension/type mapping with one of the application flags. For example: % launch -i com.omnigroup.omniweb Desktop/blah.html % launch -i org.mozilla.mozilla Desktop/blah.html would do what you expect. In the next version of launch I'm planning on adding code to open URLs directly, so you could do: % launch -i com.omnigroup.omniweb http://www.cnn.com/ and it would work properly. I'm working on other stuff right now so I won't get back to launch for a couple of months, though (unless someone wants to submit a patch :) -- =Nicholas Riley <[EMAIL PROTECTED]> | <http://www.uiuc.edu/ph/www/njriley> Pablo Research Group, Department of Computer Science and Medical Scholars Program, University of Illinois at Urbana-Champaign _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
