I've moved this work to a new branch on my repo - the vr3-asciidoc branch. It's at
https://github.com/tbpassin/leo-editor/tree/vr3-asciidoc Please get vr3 from there if you want to try the latest efforts. On Thursday, August 20, 2020 at 6:34:14 PM UTC-4, Thomas Passin wrote: > > I have been upgrading vr3 to render asciidoc nodes, mostly because of > Kevin's interest. The work is not finished, but at least vr3 will render a > single node of asciidoc. Because it is still in progress I haven't issued a > PR. But you can get it from my github repo - > > https://github.com/tbpassin/leo-editor > > The new version is in the devel branch. It is version v3.0b10. > > To render asciidoc, you need to have an asciidoc processor installed, and > the two that should work are asciidoc (from > https://asciidoc.org/index.html, and sometimes available as an > installable package on Linux), and asciidoc3 (from pypi) I haven't been > able to get asciidoc3 to work on my Windows machine, so I recommend the > former. > > The asciidoc processor needs to be available on the system path so that > vr3 can find its executable file (which could be a batch file launcher). > For asciidoc, which does not install into Python's site-packages, you can > create a new Leo setting to point to the asciidoc directory - > > @string vr3-asciidoc-path = <path-to-asciidoc-directory> > > Vr3 will run asciidoc if it finds it, otherwise it will try for > asciidoc3. More information is in the Help section > (Plugins/viewrendered3/about in the Leo menus). > > Please report any serious problems here. > -- 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/16d148d9-8eae-446c-b392-42ca790ac607o%40googlegroups.com.
