From: "Dave MacFarlane" <driusan@driusan.net>
To: 9front@9front.org
Subject: Re: [9front] str2json and jsonfmt
Date: Thu, 25 Jan 2024 08:42:05 -0500 [thread overview]
Message-ID: <0EA75CAA112ACBA77E10723AFD82E1B1@driusan.net> (raw)
In-Reply-To: <CAD3fX0NjuV=45JoAZsynyPASbYE-6hexuZMpVhMZRyVmAgXArg@mail.gmail.com>
I wrote something similar to OP's str2json which I call jsonfmt which
I use all the time, so I'm definitely in favour of including it.
If there's going to be a /bin/json/* hierarchy another candidate would
be a json/fs. I have one that I wrote for myself here:
https://github.com/driusan/fedi9/blob/front/jsonfs.c to make it easier
to deal with json in shell scripts but I don't think it's very good or
up to 9front standards (it's not well documented and it can get
crash-y when you try and re-use same /mnt/json/ctl with different
json). There may be other json/fs implementations out there in the
world.
Quoth phil9 <telephil9@gmail.com>:
> I also wrote some json tool
> (http://shithub.us/phil9/gj/HEAD/info.html) inspired by gron to make
> json greppable.
> umbraticus has a better version but I can never remember their site :)
>
> Maybe we could have all these tools in a json subdir of /bin like
> json/fmt, json/parse, json/grep
>
> On Thu, Jan 25, 2024 at 9:08 AM <cinap_lenrek@felloff.net> wrote:
> >
> > nice!
> >
> > thanks for sharing.
> >
> > this might indeed become usefull for a mangadex fetcher.
> >
> > --
> > cinap
>
next prev parent reply other threads:[~2024-01-25 13:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 5:52 Xiao-Yong Jin
2024-01-25 8:06 ` cinap_lenrek
2024-01-25 8:57 ` phil9
2024-01-25 9:17 ` chris
2024-01-25 14:03 ` Alex Musolino
2024-01-25 13:42 ` Dave MacFarlane [this message]
2024-01-25 14:57 ` cinap_lenrek
2024-01-25 15:39 ` Dave MacFarlane
2024-01-25 16:16 ` Steve simon
2024-01-26 9:34 ` umbraticus
2024-01-25 14:19 ` hiro
2024-01-26 14:53 ` ori
2024-01-26 17:28 ` Steve Simon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0EA75CAA112ACBA77E10723AFD82E1B1@driusan.net \
--to=driusan@driusan.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).