Re: [fossil-users] Command-line output format

2017-03-29 Thread Warren Young
On Mar 29, 2017, at 8:40 AM, Warren Young wrote: > > https://unix.stackexchange.com/questions/ Oops, over-edited that URL: https://unix.stackexchange.com/questions/121718/ ___ fossil-users mailing list

Re: [fossil-users] Command-line output format

2017-03-29 Thread Warren Young
On Mar 28, 2017, at 1:16 AM, Florian Balmer wrote: > > parsing JSON from shell scripts or Windows > batch files seems not so trivial. We have no lack of options for JSON parsing on POSIX type systems: https://unix.stackexchange.com/questions/ The top option, jq,

Re: [fossil-users] Command-line output format

2017-03-28 Thread j. van den hoff
On Tue, 28 Mar 2017 09:16:33 +0200, Florian Balmer wrote: Citation from: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg24841.html ... What can we do to help you move away from scripts that depend on the details of command-line output and toward

[fossil-users] Command-line output format

2017-03-28 Thread Florian Balmer
Citation from: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg24841.html > ... What can we do to help you move away from scripts that depend > on the details of command-line output and toward something that is > more likely to survive an update? ... Would it be better to run >