> Only the user can know what would be useful. totally ok for such a filetype where its just 'data' storage and definitions... dont bother with that
On Friday, July 17, 2020 at 10:17:54 AM UTC-4, Edward K. Ream wrote: > > On Friday, July 17, 2020 at 7:13:57 AM UTC-5, Edward K. Ream wrote: > > > ...a *public *json importer looks like a dubious idea, but a *private *json > importer might work as a "hidden helper" for parse-body. > > Alas not. > > json syntax suggests no natural way to divide json into nodes. Only the > user can know what would be useful. As a result, parse-body does not seem > possible, even in principle, for .json files. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/77a08c07-5320-44e0-b95c-e5d73afbebfeo%40googlegroups.com.
