Without knowing anything about the plugin, it looks like the signature of
fc.write_leo_file() is currently not the signature the plugin thinks it
is. I'd try commenting out the extra params in the plugin, and see what
what you get:
ok = self.c.fileCommands.write_Leo_file(
fileName#,
#outlineOnlyFlag=not self.opml_write_derived_files,
#toString=False, toOPML=True
)
You would have to restart Leo, or run a new Leo session, to try the changes
out.
On Monday, August 29, 2022 at 6:15:29 PM UTC-4 chr...@gmail.com wrote:
> Hi,
>
> If you want you can skip to "*Problem*" below.
>
> I'm new to Leo but not to Python, and not to the world. For 30 years,
> I've been trying to recapture the magic of MORE (and ThinkTank...) , but on
> Windows (had to switch in 1989, never used a Mac since). No way. Recently
> got fed up, got a Mac Mini M1, an iPhone and iPad, bought OmniOutliner,
> but I now only use it on IOS to exchange OPML files with Windows because
> _BREVITYALERT_. Even though I got to a decent level in Python, I never
> tried LEO because _BREVITYALERT_
>
> But THIS IS THE ONE. Wow!
>
> *Problem*
> Of course, my first message is also about a problem. I'm pretty sure I got
> the leoOPML.py plugin configuration right (file, tree, directives, body
> panel), but when I type *write-opml-file* in the mini-buffer (and by the
> way this procedure seems to be nowhere on leoeditor.com or
> davy39.github.io/leo-editor/apidoc/leo.plugins.html. Thanks, Google),
> I get this:
>
>
>
>
>
>
>
>
>
> *Traceback (most recent call last): File
> "C:\Python310\lib\site-packages\leo\core\leoKeys.py", line 2521, in
> callAltXFunction func(event) File
> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 346, in
> writeOpmlCommand c.opmlCommands.writeFile(fileName) File
> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 319, in
> writeFile ok = self.c.fileCommands.write_Leo_file(TypeError:
> FileCommands.write_Leo_file() got an unexpected keyword argument
> 'outlineOnlyFlag'*
> everytime, either with my own narrow set of parameter plugins or with the
> one in leosettings.leo.
>
> I went through the plugin code, tried to remove line 321, but then
> *Tostring=False* became unexpected too. Then I tried to learn about
> *c.filecommands*, but I thought it better to join the group and write
> this.
> ???
>
> Thanks in advance for help,
>
> Chris
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/f278306e-937e-448a-b7f0-889e649a7647n%40googlegroups.com.
