Open d3v-null opened 8 months ago
What happened if you just do carta without the browser flag?
it opens the carta url in my default browser (firefox)
some more info on what gets installed by brew:
/opt/homebrew/bin/carta
looks like this:
#!/bin/bash
/opt/homebrew/Caskroom/CARTA.app/Contents/Resources/app/carta-backend/bin/carta.sh "$@"
/opt/homebrew/Caskroom/CARTA.app/Contents/Resources/app/carta-backend/bin/carta.sh
#!/bin/bash
dirname=`dirname $0`
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null && pwd )/../etc"
export CASAPATH="../../../../$DIR linux"
$dirname/casa_data_autoupdate
$dirname/carta_backend $@ --frontend_folder=$dirname/../../
I might just add that this may be more of an issue with https://github.com/CARTAvis/homebrew-tap/ rather than carta-backend, since the packaging has changed recently, and I don't get the warning on 4.1.0 on linux.
carta --browser 'curl -a'
should I move this issue over to that repo instead?
Describe the bug
I prefer to use Carta in Chrome, which is not my default browser, so I normally launch carta like this
--browser='open -a Google\ Chrome'
This previously worked fine in version 4.0.0 (which I installed through homebrew), but something has changed in 4.1.0, so I get this error now.
It seems like the
-a
in the browser command is being interpreted as a command line argument for Carta.It doesn't like this either
To Reproduce on macOS sierra, carta v4.1.0
Expected behavior Should open Carta in Chrome like it did on v4.0.0
Platform info (please complete the following information):
Additional context Maybe the meaning of the --browser argument has changed, but if whatever is wrapping carta is not splitting shell arguments correctly, that's probably indicative of a more serious issue.
Thanks!