Dave Winer the man himself validated my file on his OPML validator, so it
works just fine. I recommend
http://validator.opml.org/ <http://validator.opml.org/>
as long as you use a URL straight from a web server, and not from Dropbox
etc. as I did.
And you can't do better than using
https://github.com/scripting/opml.org
<https://github.com/scripting/opml.org>
for questions and issues with fixing Leo OPML output, always keeping in
mind that it is an EXCHANGE FORMAT, and that less is more. And of course,
http://opml.org/spec2.opml
*Thanks* [email protected] <https://groups.google.com/>*!*
On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 [email protected] wrote:
> Shouldn't be hard to adjust the output format, I would think (not knowing
> anything about the actual plugin). Do you know of an OPML validator so
> potential fixes could be tested?
>
> On Tuesday, August 30, 2022 at 12:11:37 PM UTC-4 [email protected] wrote:
>
>> That's what I did, and the resulting file was not OPML. Check my previous
>> message:
>> https://groups.google.com/g/leo-editor/c/bV98DK9QtPI/m/m7bLQioQCgAJ
>>
>> On Tuesday, August 30, 2022 at 5:07:08 AM UTC+2 [email protected] wrote:
>>
>>> 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 [email protected] 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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/d8f27a6c-b9d7-4d28-9004-1882257735e6n%40googlegroups.com.
