Hi Edward well, after saving the @auto file the node gets restored next time, but the content of the file is not what you see in the node (body), but a special JSON file, which describes the node, it's children, even the uA's etc. Such a file is of course useless when I want to edit an arbitrary JSON file.
For me the workaround is to use @clean instead of @auto. But I still have to use your workaround the first time I open an externally generated JSON file, otherwise Leo refuses to read the file. Alternatively I can read any file, also JSON with @edit and later change to @clean, however my default @file setting (in active_path) is @clean, and that fails. Also, there seems to be no @language json I think the leo_json.py plugin should not use @auto (and @clean ...) in this way, because this behaviour is very different from the way @auto works for other languages, where the external file can be any ordinary Python, C, Lua, ... file. Rather, leo_json.py should use different directives, to make the difference clear. At the same time, I wish Leo would be able to read and write generic JSON files, including syntax highlighting. - Josef -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
