Closed sneak closed 8 years ago
sneak@pris:~$ CoreLocationCLI -once yes -format '%latitude : %longitude'
works
sneak@pris:~$ CoreLocationCLI -once yes -format 'x %latitude : %longitude'
works
sneak@pris:~$ CoreLocationCLI -once yes -format '"lat" %latitude : %longitude'
fails
sneak@pris:~$ CoreLocationCLI -once yes -format 'lat %latitude : %longitude'
works
sneak@pris:~$ CoreLocationCLI -once yes -format '{ lat %latitude : %longitude'
fails
really would defaulting to json output be so bad?
Hmmm interesting that the other ones work but that one fails.
I would love JSON output everywhere. But convention seems to be that command line tools do not output JSON. Maybe we can make a -json
option, but it would have to be streaming json.
Convention is wrong now that jq -r
exists. Also, I always use -once
.
That makes sense, -json
can imply -once
. I'm not sure how jq -r
works.
I'm not sure how
jq -r
works.
@fulldecent See the manual for jq
.
@sneak I don't think jq
can be considered a standard/convention by now. It is still far too unknown.
Why doesn't CoreLocationCLI
output all information via JSON (like accuracy, speed, direction)? Right now, -json
is a showstopper for me because it doesn't give me accuracy?
Why doesn't
CoreLocationCLI
output all information via JSON (like accuracy, speed, direction)? Right now,-json
is a showstopper for me because it doesn't give me accuracy.
bump.
Also, it seems like you made backwards-incompatible changes with v2.2.0
😢