Ah, I guess you need to install lxml for that to work. Not something that can be bundled with Leo.
On April 23, 2017 6:39:50 AM CDT, Joe Orr <joe....@gmail.com> wrote: >Oh realized I needed to add it in myLeoSettings.py. > >Did so, and got this message: > >loadOnePlugin: error importing plugin: leo.plugins.xml_edit >Traceback (most recent call last): >File "/Users/josephorr/Development/leo-editor/leo/core/leoPlugins.py", >line 502, in loadOnePlugin > __import__(moduleName) >File "/Users/josephorr/Development/leo-editor/leo/plugins/xml_edit.py", > >line 103, in <module> > from lxml import etree >ImportError: No module named lxml >loadOnePlugin: can not load enabled plugin: leo.plugins.xml_edit > >Joe > >On Sunday, April 23, 2017 at 7:31:47 AM UTC-4, Joe Orr wrote: >> >> Any tips on how to get that plugin to work? Does not show on the >plugins >> menu pulldown. Leo 5.5, Mac OS. >> >> Also, when I click on 'plugins menu' item, get raw md text in view >> rendered pane. View rendered pane does only displays raw output, both >Mac >> and Windows. >> >> Joe >> >> On Saturday, April 22, 2017 at 11:26:01 PM UTC-4, Terry Brown wrote: >>> >>> On Sat, 22 Apr 2017 16:41:40 -0700 (PDT) >>> Joe Orr <joe...@gmail.com> wrote: >>> >>> > Probably a dumb question, but how do I convert this file to Leo >>> > format: https://www.ibiblio.org/xml/examples/shakespeare/lear.xml >>> > >>> > I tried the import entry on the file menu, that didn't seem to >work. >>> >>> What do you expect it to look like when it's imported? >>> >>> You could use an `@auto lear.xml`, hmm, apparently that's no >different >>> to `@edit lear.xml`, just a single node import of the XML. >>> >>> Perhaps try the xml_edit plugin. I just loaded it with that, took a > >>> little time on my relatively fast desktop, so be patient. I suspect > >>> that gives you what you're looking for demo wise. >>> >>> Cheers -Terry >>> >>> > I can write an XSL stylesheet to do the conversion if necessary, >but >>> > it that is the case, is there a guide to the Leo file format? (I >can >>> > figure it out my looking at it, just would like to know if there >are >>> > things I shouldn't miss). >>> > >>> > Joe >>> > >>> > On Sunday, April 16, 2017 at 7:33:58 AM UTC-4, Edward K. Ream >wrote: >>> > > >>> > > The new code is simpler than the old, and should be more robust >in >>> > > the face of dubious syntax. All unit tests pass, and Rob's >recent >>> > > files import correctly. Still, more real-world testing is >>> > > required. Please report any problems immediately. >>> > > >>> > > Edward >>> > > >>> > > P.S. The code that handles "<", "</", ">" and "/>" has changed >as >>> > > follows: >>> > > >>> > > 1. The stack of open tags is now "stateless". That is, it >contains >>> > > only tags. >>> > > 2. The stack now contains *all* open tags, including void tags >and >>> > > tags not in @data import_html_tags. >>> > > >>> > > The new code completely ignores ">" tags except when the top of >the >>> > > stack is a void tag. This is an important simplification. It >>> > > should allow more robust error checking. We shall see... >>> > > >>> > > EKR >>> >> > >-- >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. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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.
