(Oh -- and I tried with "" as well as with ''). Robby
On Sat, Feb 28, 2009 at 7:01 AM, Robby Findler <robby at eecs.northwestern.edu> wrote: > On Sat, Feb 28, 2009 at 6:42 AM, Eli Barzilay <eli at barzilay.org> wrote: >> On Feb 28, Thomas Chust wrote: >>> 2009-02.28 Robby Findler <robby at eecs.northwestern.edu>: >>> > [...] >>> > browser-run: process execute failed: (#<path:/usr/bin/osascript> "-e" >>> > "open location >>> > \"file:///Users/robby/Library/PLT%20Scheme/4.1.4.3/doc/search/index.html?q=bitmap%25\"") >>> > [...] >>> >>> Hello, >>> >>> out of curiosity: Is there any particular reason why PLT Scheme >>> doesn't use the LaunchServices API to open the URL instead of >>> executing an external command? >> >> Much easier to implement, and extremely negligible cost (compared to >> starting your browser and making it render a documentation page). > > Maybe it is time to use launchservices, since we're having problems > passing arguments, apparently. > >>> And if it is necessary to use an external command, why does it have >>> to be that complicated instead of just running /usr/bin/open <URL>? >> >> That, I don't know. ?Robby -- while you're having this problem (it >> looks like it's not consistent), maybe you can try to change to the >> above and see if it works better? ?(The change in net/sendurl.ss >> should be very easy.) > I hit f1 in exactly the same place and now I get no error (with > osascript). Boy, that's annoying. > > When I use 'open' I get this: > > The file > /Users/robby/svn/plt/collects/net/'file:/Users/robby/Library/PLT%20Scheme/4.1.4.3/doc/search/index.html?q=help' > does not exist. > browser-run: process execute failed: (#<path:/usr/bin/open> > "'file:///Users/robby/Library/PLT%20Scheme/4.1.4.3/doc/search/index.html?q=help'") > > Robby >
