These enhancements to VR3 are much appreciated. Some observations you already may be aware of...
I noticed that with Node headline *@pdf* Body text is *N:/leo/example.pdf* With vr3-show command given, when I select node the pdf shows in vr3 pane. Where the Node headline does not exactly match the Body text e.g. : Node headline *@pdf N:/leo* Body text is *N:/leo/example.pdf* When I select node it displays a file manager view of the N:/leo/ folder. This is quite useful to preview graphic files with VR3. Select a file and it shows in VR3 pane. When the file manager appears this message shows in log pane: js: crbug/1173575, non-JS module files deprecated. On Wednesday, January 8, 2025 at 3:55:11 AM UTC+11 [email protected] wrote: > I have added support for *@pdf* nodes to VR3. It's similar to the same > support in the viewrendered plugin that was added recently. > > A node whose headline starts with *@pdf *and whose headline or body > contains a path to a .pdf file on the same computer will display the > rendered PDF in the vr3 pane. The path can be either absolute or relative > to the path in effect at the node. It must use "/" for path separators, > and must NOT start with *file: * > > If the path is in the body, it must be the first line of the the body. > You can have any other text after that first line, so you can include > comments about the file. This feature is one of the differences in the way > that VR and VR3 process *@pdf* nodes. > > If both the headline and the body contain a valid path, the one in the > headline will be used. > > I forgot to update the plugin's docstring, and I'll submit a PR for that > soon. > > I'm not planning to add support for *@mathjax* nodes because VR3 already > supports mathjax embedded within RsT, MD, and Asciidoc nodes, and does it > more flexibly in that mathjax, ordinary text, and images can be included in > any of those nodes. > -- 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 visit https://groups.google.com/d/msgid/leo-editor/95901cb0-3685-4c0f-a594-fb9ba13aaefbn%40googlegroups.com.
