Re: leo-to-html HAS STOPPED WORKING

[chr...@gmail.com]

OK, it *WORKS*.
My correct path was indeed C:\leo-editor-master\leo\plugins\, and I now 
remember that what's in 
C:\Python311\Lib\site-packages\leo-6.7.7.dist-info\
(NOT \leo) is a bunch of stuff that I guessed was like pointing to the 
actual source directory (leo-editor-master). I downloaded the plugin file 
following your instructions, and the file had a couple hundred bytes less 
than my clumsy cut-and-paste of the code. I should have thought of looking 
up the code of leo_to_html.py: I had noticed the difference of menu name  
in its doc and could have fixed it, but without a complete, deep, 
well-organized documentation, to the non-advanced-IT-professional Leo is 
such a black box that the idea didn't cross my mind.

*THANK YOU SO MUCH THOMAS!* I got the job done just as my nightly backups 
started, ruthlessly hogging the CPU of the laptop I was using.

By the way, several other plugins don't work anymore. I forgot which ones.

The "outside of the python directory" LEO-EDITOR-MASTER trick is a very 
good one. It makes updating both python and Leo sources much easier, 
without having to create environments etc. It seems to have disappeared 
from the "downloading Leo" webpage, though. There was a "downloading 
sources" section, and I always assumed that the other download methods were 
providing a kind of half "compiled' Leo, so I never used them. Is that the 
case? now the whole sources package can be downloaded from github, I guess.

"Leo is a PIM" is not really true anymore.
Without the whole professional programmer's knowledge of all the 
intricacies of  process and online platforms such as github and all the 
extra software used to put together and install something like Leo, the guy 
like me for whom computers are first and foremost (addictive) tools to 
achieve other things, Leo's complexity has evolved so much that it is now 
only a great tool for programmers.

I'm planning to go back to OmniOutliner: I'll have my outlines (with 
pictures) on my Mac, on my PCs through Teamviewer, and on my iPad and 
iPhone without having to convert them to OPML with a script. I won't have 
to go through reams of scattershot documentations at every turn of the road.

It was an interesting adventure...

Ciao!
On Monday, May 13, 2024 at 10:06:08 PM UTC tbp1...@gmail.com wrote:

> Yes, once you find the leo-to-html.py file, download it and then copy into 
> your Python install's *site-packages/leo/plugins* directory.
>
> To find that location, open a terminal or console and run
>
> py -m pip show leo
>
> NOTE - use the actual command that you use to run Python if it's not 
> "py".  The response will include a line that tells you where the right 
> *site-packages* directory is.  On my system it's
>
> Location: C:\Users\tom\AppData\Roaming\Python\Python312\site-packages
>
> Here's a step-by-step now that's in the main Leo-Editor repository.  
> First, navigate to the top of the repo 
> <https://github.com/leo-editor/leo-editor>. Select the *Code* tab if it's 
> not selected. Then select the *devel* branch in the branch selector box, 
> near the upper left.  Then navigate to *leo/plugins* page and scroll down 
> until you find the link to our file, *leo-html.py*.  Click that link.
> In  that page, the one for our file,  notice near the upper right that 
> there is a box labeled "Raw".  There is a download icon next to it.  Click 
> that to download our file.
>
> Please post about any apparent bugs you find - I haven't given this fix 
> much of a workout.  I hoped to get you running as quickly as possible since 
> you sounded as if you depend a lot on the plugin.
> On Monday, May 13, 2024 at 5:48:26 PM UTC-4 chr...@gmail.com wrote:
>
>> On Monday, May 13, 2024 at 8:06:29 PM UTC tbp1...@gmail.com wrote:
>>
>> I have created a pull request, 3907 
>> <https://github.com/leo-editor/leo-editor/pull/3907>, that gets this 
>> plugin working again.  At least, it works when outputting just the 
>> headlines. 
>>
>> If anyone wants to try it out before the PR gets merged into the devel 
>> branch, you can follow the link in the Github PR page to my repository and 
>> get the file there.
>>
>>
>> Thanks Thomas, I half understand "Github PR page to my repository"... is 
>> the name of the file LEO-TO-HTML.? and do I replace the same file in my 
>> installation?
>>
>

-- 
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/e99dd7ac-740f-463b-bfa1-c60fe79783den%40googlegroups.com.

Re: leo-to-html HAS STOPPED WORKING

[chr...@gmail.com]

OK,  so that's why it wouldn't work: I copied it in 
C:\leo-editor-master\leo\plugins\
I don't even know the difference betweenl eo-editor-master and  the install 
that's in Python site-packages. I'MM A SELF-TAUGHT GUY except for one 
semester of BASIC on Apple 2 around 1982, fer chrissakes. But I did surf 
the wave all along, and among other things I even learned C in a week and 
wrote an online financial datafeed custom on-demand retrieval program for 
UBS in the early 90s, in another two weeks, dammit.
Only ever used Github to download useful stuff. I couldn't find how to 
download the plugin so I copied the text, and of course the first time it 
wasn't fully expanded.
Gonna try what you wrote now.

On Monday, May 13, 2024 at 10:06:08 PM UTC tbp1...@gmail.com wrote:

> Yes, once you find the leo-to-html.py file, download it and then copy into 
> your Python install's *site-packages/leo/plugins* directory.
>
> To find that location, open a terminal or console and run
>
> py -m pip show leo
>
> NOTE - use the actual command that you use to run Python if it's not 
> "py".  The response will include a line that tells you where the right 
> *site-packages* directory is.  On my system it's
>
> Location: C:\Users\tom\AppData\Roaming\Python\Python312\site-packages
>
> Here's a step-by-step now that's in the main Leo-Editor repository.  
> First, navigate to the top of the repo 
> <https://github.com/leo-editor/leo-editor>. Select the *Code* tab if it's 
> not selected. Then select the *devel* branch in the branch selector box, 
> near the upper left.  Then navigate to *leo/plugins* page and scroll down 
> until you find the link to our file, *leo-html.py*.  Click that link.
> In  that page, the one for our file,  notice near the upper right that 
> there is a box labeled "Raw".  There is a download icon next to it.  Click 
> that to download our file.
>
> Please post about any apparent bugs you find - I haven't given this fix 
> much of a workout.  I hoped to get you running as quickly as possible since 
> you sounded as if you depend a lot on the plugin.
> On Monday, May 13, 2024 at 5:48:26 PM UTC-4 chr...@gmail.com wrote:
>
>> On Monday, May 13, 2024 at 8:06:29 PM UTC tbp1...@gmail.com wrote:
>>
>> I have created a pull request, 3907 
>> <https://github.com/leo-editor/leo-editor/pull/3907>, that gets this 
>> plugin working again.  At least, it works when outputting just the 
>> headlines. 
>>
>> If anyone wants to try it out before the PR gets merged into the devel 
>> branch, you can follow the link in the Github PR page to my repository and 
>> get the file there.
>>
>>
>> Thanks Thomas, I half understand "Github PR page to my repository"... is 
>> the name of the file LEO-TO-HTML.? and do I replace the same file in my 
>> installation?
>>
>

-- 
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/3037f907-5a61-4618-b942-b1fea353ba96n%40googlegroups.com.

Re: leo-to-html HAS STOPPED WORKING

[chr...@gmail.com]

OK, found it

On Monday, May 13, 2024 at 9:48:26 PM UTC chr...@gmail.com wrote:

> On Monday, May 13, 2024 at 8:06:29 PM UTC tbp1...@gmail.com wrote:
>
> I have created a pull request, 3907 
> <https://github.com/leo-editor/leo-editor/pull/3907>, that gets this 
> plugin working again.  At least, it works when outputting just the 
> headlines. 
>
> If anyone wants to try it out before the PR gets merged into the devel 
> branch, you can follow the link in the Github PR page to my repository and 
> get the file there.
>
>
> Thanks Thomas, I half understand "Github PR page to my repository"... is 
> the name of the file LEO-TO-HTML.? and do I replace the same file in my 
> installation?
>

-- 
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/95e5ab8c-f665-4c5c-ba60-675d288294a8n%40googlegroups.com.

Re: leo-to-html HAS STOPPED WORKING

[chr...@gmail.com]

On Monday, May 13, 2024 at 8:06:29 PM UTC tbp1...@gmail.com wrote:

I have created a pull request, 3907 
, that gets this plugin 
working again.  At least, it works when outputting just the headlines. 

If anyone wants to try it out before the PR gets merged into the devel 
branch, you can follow the link in the Github PR page to my repository and 
get the file there.


Thanks Thomas, I half understand "Github PR page to my repository"... is 
the name of the file LEO-TO-HTML.? and do I replace the same file in my 
installation?

-- 
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/1919ef53-5348-47d1-98b2-13508e27325dn%40googlegroups.com.

Re: leo-to-html HAS STOPPED WORKING

[chr...@gmail.com]

@tbp1...@gmail.com
*What is the latest release where you know it worked?*

Maybe November, not sure at all. 

-- 
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/581cdcf8-ad4c-433a-9250-6bec577cc2fbn%40googlegroups.com.

leo-to-html HAS STOPPED WORKING

[chr...@gmail.com]

*...and it's a major-urgent-pain-in-the-neck for me!*

- None of the plugin submenus appear in the File > Export Files... menu
- The plugin is correctly enabled in myLeoSettings.leo
- There is no "@bool leo_to_html_no_menus = True" anywhere

- I have a  ~450 headlines outline, so I tried with a 3-line
"test1"
"test2"-"test3" outline, here is what I get by running
"export-html-bullet" from the minibuffer:





















*Leo Log WindowLeo 6.7.7Python 3.11.8, PyQt version 5.15.2Windows 10 AMD64 
(build 10.0.19045) SP0leo_to_html: running ...Traceback (most recent call 
last):  File "C:\leo-editor-master\leo\core\leoKeys.py", line 2501, in 
callAltXFunctionfunc(event)  File 
"C:\leo-editor-master\leo\plugins\leo_to_html.py", line 248, in 
export_html_headself.export_html(bullet='head')  File 
"C:\leo-editor-master\leo\plugins\leo_to_html.py", line 236, in 
export_htmlhtml.main(bullet=bullet, show=show, node=node)  File 
"C:\leo-editor-master\leo\plugins\leo_to_html.py", line 453, in main
self.do_xhtml(node)  File 
"C:\leo-editor-master\leo\plugins\leo_to_html.py", line 353, in do_xhtml
self.doItemHeadlineTags(root)  File 
"C:\leo-editor-master\leo\plugins\leo_to_html.py", line 373, in 
doItemHeadlineTagsself.doHeadline(p, level)  File 
"C:\leo-editor-master\leo\plugins\leo_to_html.py", line 408, in doHeadline  
  self.xhtml.append(self.openHeadlineString % h + headline + 
self.closeHeadlineString % h)^^AttributeError: 'Leo_to_HTML' 
object has no attribute 'xhtml'*

same result with "export-html-head"

- The Toolbar Menu -> Plugins ->Properties results in this in the log 
window:
*Properties menu not supported for Qt gui*

"export-html-node" doesn't work either.

HELP!






-- 
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/a86d7500-23af-4994-bc51-d8e0a6f776b0n%40googlegroups.com.

Re: Installation instructions typo

[chr...@gmail.com]

Thanks!

On Monday, February 19, 2024 at 2:26:46 AM UTC+1 Edward K. Ream wrote:

> On Sun, Feb 18, 2024 at 7:15 PM chr...@gmail.com  wrote:
>
>> Can someone finally correct this paragraph:
>> https://leo-editor.github.io/leo-editor/installing.html#id7
>>
>> The command should be either
>>  pip install (ONE DASH)e C:\path\to\leo-editor 
>> or
>>  pip install  (TWO DASHES)editable C:\path\to\leo-editor
>> but certainly not
>>  pip install (EM DASH)editable C:\path\to\leo-editor
>>
>> I get stuck on this at EVERY new version of Leo. My memory is fine, thank 
>> you, but it refuses to waste a single electron on such nuisance.
>>
>> Thank you.
>>
>
> Will do. I was not aware of this typo.
>
> Edward
>

-- 
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/a0a15b87-54ba-43e0-a1c1-2ad8a06b357bn%40googlegroups.com.

Installation instructions typo

[chr...@gmail.com]

Can someone finally correct this paragraph:
https://leo-editor.github.io/leo-editor/installing.html#id7

The command should be either
 pip install (ONE DASH)e C:\path\to\leo-editor 
or
 pip install  (TWO DASHES)editable C:\path\to\leo-editor
but certainly not
 pip install (EM DASH)editable C:\path\to\leo-editor

I get stuck on this at EVERY new version of Leo. My memory is fine, thank 
you, but it refuses to waste a single electron on such nuisance.

Thank you.

-- 
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/2e0deed9-3d92-47f7-828d-6f0520b21dc9n%40googlegroups.com.

Re: remove enter key assignment

[chr...@gmail.com]

OK, I got it.

On Tuesday, August 15, 2023 at 11:06:18 AM UTC+2 chr...@gmail.com wrote:

> Hello,
>
> How do I "unassign" the Enter key from switching to the text panel?
> I've looked in settings and in the code but couldn't find where this is 
> defined.
>
> Thanks in advance
>
> Chris
> Windows 10/11
> Leo 6.7.2
>

-- 
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/18a8628d-fcfb-409f-b4db-b42a832117b4n%40googlegroups.com.

remove enter key assignment

[chr...@gmail.com]

Hello,

How do I "unassign" the Enter key from switching to the text panel?
I've looked in settings and in the code but couldn't find where this is 
defined.

Thanks in advance

Chris
Windows 10/11
Leo 6.7.2

-- 
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/6afb72f8-e702-467e-874d-27957a41d190n%40googlegroups.com.

A couple of questions and remarks about the UI

[chr...@gmail.com]

Hello,

1. "Outline Indicators" in settings: are they the v-shaped gizmo icons that 
expand or collapse trees?

2.  If yes, I can't replace them by linking to icons such as those in the 
"plusminus" subfolder. is this functionality deprecated? I'm not using a 
theme, and my settings start with
@bool color_theme_is_dark = False
@string theme-name = None
I succeeded in replacing the headline boxes by placing mine at the top 
level of the "icons" subfolder and naming them box## accordingly (replacing 
the original files).

3. Multi-selecting headlines: click on headline, and shift-click on another 
one above or below. The first clicked headline gets deselected, unlike 
every other application in the universe. Please consider fixing this.

4. After all these years, "Demote node / Promote node" should really be 
called what it does: "Demote children / Promote children", or "Demote 
subtree / Promote Subtree".

Best Regards,

Chris R.

-- 
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/7e92c523-ce75-424d-813e-7185b46007aan%40googlegroups.com.

Re: Two standard outline editing commands

[chr...@gmail.com]

Thanks a lot guys, now I've got plenty enough to get going
On Friday, March 3, 2023 at 1:08:54 AM UTC+1 tbp1...@gmail.com wrote:

> On Thursday, March 2, 2023 at 3:41:48 PM UTC-5 chr...@gmail.com wrote:
>
> If these two indeed don't exist, can they be added by scripting? via a 
> plugin? Maybe I could dot hat, but am not yet quite sure yet, gotta read 
> more doc.
>
>
> The best way to proceed, IMHO, is to develop the script in your workbook.  
> I would assign it to a button during development using the *script-button*
>  button. 
>
> Once it is working to your satisfaction, copy the code into the 
> *@settings* tree of *myLeoSettings.leo* as an *@command* node, giving it 
> a suitable name.  Then the next time you restart Leo, that command will be 
> available to all open outlines.
>
> This how I develop most of my scripts, at least the ones that create new 
> commands.  I suggest that you prefix your commands with a recognizable 
> prefix, such as your initials.  Then when you do command completion in the 
> minibuffer, you will see only your own commands.  This reduces the load on 
> your memory, and turns out to be really convenient.  For example, I have a 
> command named *tp-outline-from-node*.  It's also helpful to prefix 
> experimental commands with, say, *x-*.  When the command is ready for 
> prime time then change its prefix.
>
> If you find that you are using the command often, you could create an 
> *@button* node for it in *myLeoSettings.leo*.  But in some outlines, 
> space for another button may be scarce.  It is also possible (not hard) to 
> add the command to an existing menu, or even to create your own custom menu 
> and add your command as an item to it (I call my own menu *Local).  *You 
> can also bind it to a keystroke, but I wouldn't do that unless you use it 
> all the time - spare keystrokes are scarce and it can be hard to find the 
> binding after you forget.
>
> If you have the script for the command in *myLeoSettings.leo* and you 
> find a bug or would like to change how it works, you can edit it right in 
> the outline, and your changes will be in effect the next time the command 
> is invoked - no need to restart Leo.
>

-- 
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/4e828779-729c-425d-8293-d74116215418n%40googlegroups.com.

Two standard outline editing commands

[chr...@gmail.com]

Hi,

- I can't find an *insert-sibling *command, by which a headline can be 
created below the last offspring of the currently active *expanded* parent, 
at the same level as that active parent. 

- Same thing for a *split-headline* command, by which while in headline 
text editing mode, we can split the headline, transferring all text 
following the caret into a new sibling, right below the current headline.

If these two indeed don't exist, can they be added by scripting? via a 
plugin? Maybe I could dot hat, but am not yet quite sure yet, gotta read 
more doc.
Or should I present this as a feature request, if such a thing is accepted 
for consideration in this group?

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/f53fc11d-752c-4ab2-9c9f-c78a25a68528n%40googlegroups.com.

Re: Using MacPorts to deploy Leo on macOS computers

[chr...@gmail.com]

I totally agree. I recently tried both Homebrew and MacPorts for the first 
time to install Python, and I found MacPorts better designed, with better 
and clearer information about the process, no tiresome jargon, better 
utilities for package management, and an altogether more satisfying 
experience.

For example, compare Portfile Development 
 (and following 
pages), with Formula Cookbook  ...

Until we get a Leo Port,  and since Installing Leo on MacOs 10.7 (Lion) and 
later  is 11 years-old and 
obsolete, and as I'm using an M1 Mac with Monterey, I'm going to try How to 
install Leo under M1 chip macOS 12.* 

Wish me good luck :)
On Saturday, February 27, 2021 at 9:23:29 PM UTC+1 David Szent-Györgyi 
wrote:

> Has anyone taken a recent look at MacPorts for deploying Leo? 
>
> I know that using Homebrew to install Leo is the current recommendation. 
> Homebrew has for years installed in */usr/local* on Intel Macs, and is 
> now forced by Apple's tightening of access to that folder to install in 
> */opt/homebrew* on Apple Silicon Macs, which come with *macOS 11* "Big 
> Sur";  the recommendation for the Intel Mac remains */usr/local*. 
>
> You might call me old school, but MacPorts is my preferred system for 
> deploying open-source software on the Mac I live in for work. MacPorts 
> already installs under */opt*, basing its filesystem hierarchy under 
> */opt/local. *It can install precompiled binaries when available; it can 
> compile everything from source code, pulling that from GitHub as needed. 
>
> A custom installation can base the MacPorts filesystem in another folder 
> underneath */opt*, such as */opt/leo-editor*. Such a custom installation 
> requires compiling everything from source - no small job if one installs 
> Python and Qt - but provides the option of installing Leo with all 
> dependencies, keeping that installation independent of other software. 
>
> I can forsee separate installations, one with custom installation under 
> */opt/leo-editor *for work on development of Leo, one with the default 
> installation under */opt/local* for day-to-day use. 
>
> MacPorts is written to install without stepping on software bundled with 
> the operating system - and without relying on Apple to deliver the most 
> recent releases of that software (such as Python!). MacPorts has good 
> support for Python and for Qt, and the range of software that it supports 
> means that work is already done for supporting specific versions of Python 
> and Qt. All that would be needed would be a "portfile" that tells MacPorts 
> how to install Leo. 
>
> It is possible to use MacPorts to deploy macOS Applications, which would 
> in Leo's case be a launcher that would run the MacPorts-hosted Python and 
> use that to launch the MacPorts-hosted Leo. 
>

-- 
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/0b652b50-ed2d-4aa6-9cad-dcbb2027ac57n%40googlegroups.com.

Re: newbie stuck

[chr...@gmail.com]

OK, but all I can see here is  tbp1...@gmail.com 

On Thursday, September 1, 2022 at 1:33:56 AM UTC+2 tbp1...@gmail.com wrote:

> I've done some Leo development, both plugins and internals.  I'm not very 
> familiar with most of Leo and not at all with this plugin.  If you can get 
> an email to me at my gmail address, I'll send you the email I actually want 
> to use, and maybe we can make some progress.
>
> On Wednesday, August 31, 2022 at 5:52:38 PM UTC-4 chr...@gmail.com wrote:
>
>> tbp1...@gmail.com <https://groups.google.com/>, I don't know if you are 
>> a developer or member of the Leo team, so I'm not sure if the info I'm 
>> sending is useful, please let me know. 
>>
>> You may already know about this, but there are two leoOPML.py settings 
>> that were implemented for the integration of body text into the OPML file:
>> @bool opml_use_outline_elements = True
>> @bool opml_write_body_text = True
>>
>> and the one about writing  elements (why? I know nothing about vnodes 
>> etc., but I suppose they're useless outside of Leo, so they have no place 
>> in OPML)
>> @bool opml_write_leo_globals_attributes = False
>>
>> It seems no XML schema or DTD means anything goes with the names of 
>> attributes in OPML. One of the outliners I tried offered the possibility of 
>> changing the name of the first outline attribute  in its .ini file for OPML 
>> import/export. I found this clever.
>> OmniOutliner Pro follows the spec 2.0 for the first attribute, calling it 
>> "text", and then it's the names of columns for further attributes.  leoOPML 
>> currently would uses  for the body text, apparently. I suppose 
>> accepting anything that comes in for that "body text" second attribute 
>> during import and keeping it for export would be a good idea. If the file 
>> is first exported by Leo, then of course  is fine. Additional 
>> @settings could be used to clarify this, or maybe not. I hope I'm not 
>> making a fool of myself here...
>>
>>
>> On Wednesday, August 31, 2022 at 5:06:53 PM UTC+2 tbp1...@gmail.com 
>> wrote:
>>
>>> Here is Dave (Winer)'s spec <http://opml.org/spec2.opml>.  I would 
>>> think that there would be an XML schema (or maybe a DTD would be able to 
>>> the the joib) somewhere that could be used for validating an OPML file, but 
>>> I didn't find one in a very hasty search.
>>>
>>> Since OPML only includes what Leo calls headline text, I'm wondering if 
>>> there would ever be any use for text in (Leo) node bodies.  An OPML outline 
>>> node can contain other information besides the headline text, so maybe 
>>> that's why the plugin may deal with Leo's user attributes - the info has to 
>>> go somewhere.  
>>>
>>> Is it the case, @chr, that you want to round-trip OPML files with other 
>>> applications with full fidelity (except maybe data about an editor's 
>>> state)?  Or do you only need to include a subset of information?
>>>
>>>
>>>
>>> On Wednesday, August 31, 2022 at 10:13:37 AM UTC-4 chr...@gmail.com 
>>> wrote:
>>>
>>>> I found only one public one at http://validator.opml.org/ (website and 
>>>> validator by Dave Winer, the original OPML guy, still at the wheel), but 
>>>> it 
>>>> doesn't seem to work so well.
>>>> I submitted an issue at 
>>>> https://github.com/scripting/opml.org/issues/6#issue-1357384900
>>>>
>>>>
>>>> On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 
>>>> 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 chr...@gmail.com 
>>>>> 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 tbp1...@gmail.com 
>>>>>> 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 i

Re: newbie stuck

[chr...@gmail.com]

 tbp1...@gmail.com <https://groups.google.com/>, I don't know if you are a 
developer or member of the Leo team, so I'm not sure if the info I'm 
sending is useful, please let me know. 

You may already know about this, but there are two leoOPML.py settings that 
were implemented for the integration of body text into the OPML file:
@bool opml_use_outline_elements = True
@bool opml_write_body_text = True

and the one about writing  elements (why? I know nothing about vnodes 
etc., but I suppose they're useless outside of Leo, so they have no place 
in OPML)
@bool opml_write_leo_globals_attributes = False

It seems no XML schema or DTD means anything goes with the names of 
attributes in OPML. One of the outliners I tried offered the possibility of 
changing the name of the first outline attribute  in its .ini file for OPML 
import/export. I found this clever.
OmniOutliner Pro follows the spec 2.0 for the first attribute, calling it 
"text", and then it's the names of columns for further attributes.  leoOPML 
currently would uses  for the body text, apparently. I suppose 
accepting anything that comes in for that "body text" second attribute 
during import and keeping it for export would be a good idea. If the file 
is first exported by Leo, then of course  is fine. Additional 
@settings could be used to clarify this, or maybe not. I hope I'm not 
making a fool of myself here...


On Wednesday, August 31, 2022 at 5:06:53 PM UTC+2 tbp1...@gmail.com wrote:

> Here is Dave (Winer)'s spec <http://opml.org/spec2.opml>.  I would think 
> that there would be an XML schema (or maybe a DTD would be able to the the 
> joib) somewhere that could be used for validating an OPML file, but I 
> didn't find one in a very hasty search.
>
> Since OPML only includes what Leo calls headline text, I'm wondering if 
> there would ever be any use for text in (Leo) node bodies.  An OPML outline 
> node can contain other information besides the headline text, so maybe 
> that's why the plugin may deal with Leo's user attributes - the info has to 
> go somewhere.  
>
> Is it the case, @chr, that you want to round-trip OPML files with other 
> applications with full fidelity (except maybe data about an editor's 
> state)?  Or do you only need to include a subset of information?
>
>
>
> On Wednesday, August 31, 2022 at 10:13:37 AM UTC-4 chr...@gmail.com wrote:
>
>> I found only one public one at http://validator.opml.org/ (website and 
>> validator by Dave Winer, the original OPML guy, still at the wheel), but it 
>> doesn't seem to work so well.
>> I submitted an issue at 
>> https://github.com/scripting/opml.org/issues/6#issue-1357384900
>>
>>
>> On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 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 chr...@gmail.com 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 tbp1...@gmail.com 
>>>> 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 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, 

Re: newbie stuck

[chr...@gmail.com]

 tbp1...@gmail.com <https://groups.google.com/>, I don't know if you are a 
developer or member of the Leo team, so I'm not sure if the info I'm 
sending is useful, please let me know. 

You may already know about this, but there are two leoOPML.py settings that 
were implemented for the integration of body text into the OPML file:
@bool opml_use_outline_elements = True
@bool opml_write_body_text = True

and the one about writing  elements:
@bool opml_write_leo_globals_attributes = False

Also, one of the outliners I tried offered the possibility of changing the 
name of the first attribute of the outline before exporting the .opml file. 
I found this clever. As the body text attribute is called  in 
leoOPML.py, but OmniOutliner allows columns naming and I guess no schema 
means anything goes with other OPML-capable programs, I suppose accepting 
anything that comes in for that second attribute during import and keeping 
it for export would be a good idea. If the file is first exported by Leo, 
then of course  is fine. I hope I'm not making a fool of myself 
here...

Chris
On Wednesday, August 31, 2022 at 5:06:53 PM UTC+2 tbp1...@gmail.com wrote:

> Here is Dave (Winer)'s spec <http://opml.org/spec2.opml>.  I would think 
> that there would be an XML schema (or maybe a DTD would be able to the the 
> joib) somewhere that could be used for validating an OPML file, but I 
> didn't find one in a very hasty search.
>
> Since OPML only includes what Leo calls headline text, I'm wondering if 
> there would ever be any use for text in (Leo) node bodies.  An OPML outline 
> node can contain other information besides the headline text, so maybe 
> that's why the plugin may deal with Leo's user attributes - the info has to 
> go somewhere.  
>
> Is it the case, @chr, that you want to round-trip OPML files with other 
> applications with full fidelity (except maybe data about an editor's 
> state)?  Or do you only need to include a subset of information?
>
>
>
> On Wednesday, August 31, 2022 at 10:13:37 AM UTC-4 chr...@gmail.com wrote:
>
>> I found only one public one at http://validator.opml.org/ (website and 
>> validator by Dave Winer, the original OPML guy, still at the wheel), but it 
>> doesn't seem to work so well.
>> I submitted an issue at 
>> https://github.com/scripting/opml.org/issues/6#issue-1357384900
>>
>>
>> On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 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 chr...@gmail.com 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 tbp1...@gmail.com 
>>>> 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 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_
>>>>>>
>>

Re: newbie stuck

[chr...@gmail.com]

 tbp1...@gmail.com, I don't know if you are a developer or member of the 
Leo team, so I'm not sure if the info I'm sending is useful, please let me 
know. 

You may already know about this, but I'll mention the two leoOPML.py 
settings that were planned in leOPML.py for the integration of body text 
into the OPML file:
@bool opml_use_outline_elements = True
@bool opml_write_body_text = True

and the one about writing  elements:
@bool opml_write_leo_globals_attributes = False

chris

On Wednesday, August 31, 2022 at 5:06:53 PM UTC+2 tbp1...@gmail.com wrote:

> Here is Dave (Winer)'s spec <http://opml.org/spec2.opml>.  I would think 
> that there would be an XML schema (or maybe a DTD would be able to the the 
> joib) somewhere that could be used for validating an OPML file, but I 
> didn't find one in a very hasty search.
>
> Since OPML only includes what Leo calls headline text, I'm wondering if 
> there would ever be any use for text in (Leo) node bodies.  An OPML outline 
> node can contain other information besides the headline text, so maybe 
> that's why the plugin may deal with Leo's user attributes - the info has to 
> go somewhere.  
>
> Is it the case, @chr, that you want to round-trip OPML files with other 
> applications with full fidelity (except maybe data about an editor's 
> state)?  Or do you only need to include a subset of information?
>
>
>
> On Wednesday, August 31, 2022 at 10:13:37 AM UTC-4 chr...@gmail.com wrote:
>
>> I found only one public one at http://validator.opml.org/ (website and 
>> validator by Dave Winer, the original OPML guy, still at the wheel), but it 
>> doesn't seem to work so well.
>> I submitted an issue at 
>> https://github.com/scripting/opml.org/issues/6#issue-1357384900
>>
>>
>> On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 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 chr...@gmail.com 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 tbp1...@gmail.com 
>>>> 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 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, 
>>>>>> G

Re: newbie stuck

[chr...@gmail.com]

Attached: two-column OmniOutliner Pro OPML file.

Chris

On Wednesday, August 31, 2022 at 5:06:53 PM UTC+2 tbp1...@gmail.com wrote:

> Here is Dave (Winer)'s spec <http://opml.org/spec2.opml>.  I would think 
> that there would be an XML schema (or maybe a DTD would be able to the the 
> joib) somewhere that could be used for validating an OPML file, but I 
> didn't find one in a very hasty search.
>
> Since OPML only includes what Leo calls headline text, I'm wondering if 
> there would ever be any use for text in (Leo) node bodies.  An OPML outline 
> node can contain other information besides the headline text, so maybe 
> that's why the plugin may deal with Leo's user attributes - the info has to 
> go somewhere.  
>
> Is it the case, @chr, that you want to round-trip OPML files with other 
> applications with full fidelity (except maybe data about an editor's 
> state)?  Or do you only need to include a subset of information?
>
>
>
> On Wednesday, August 31, 2022 at 10:13:37 AM UTC-4 chr...@gmail.com wrote:
>
>> I found only one public one at http://validator.opml.org/ (website and 
>> validator by Dave Winer, the original OPML guy, still at the wheel), but it 
>> doesn't seem to work so well.
>> I submitted an issue at 
>> https://github.com/scripting/opml.org/issues/6#issue-1357384900
>>
>>
>> On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 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 chr...@gmail.com 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 tbp1...@gmail.com 
>>>> 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 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 
>

Re: newbie stuck

[chr...@gmail.com]

 I believe there is no schema or DTD, unfortunately. You could ask why at 
the github link I posted just before (and deleted and re-edited several 
times!)
During my many test of Windows outliners, I remember that one interpreted 
an OmniOutliner column (each headline can have columns), which was also 
present in the OmniOutliner-output OPML file. The column was interpreted as 
an extra attribute of the headline (or maybe a "sub-attribute", if there's 
such a thing in XML?)
Strangely, the Windows program showed it ABOVE each headline (maybe because 
of alphabetical sorting, because the headline column was call "Topic" and 
the second column "Description"), slightly offset to the right, and it was 
editable. So, of course, it would be great if the *TEXT *of the body pane 
could pass into the OPML file! I Other content would not pass through. I 
hope OmniOutliner would show it as a column, but having not read the whole 
OPML 2.0 spec, I don't know how that works. I'm willing to reinstall all 
those dodgy Windows "outliners" to test this, if you want.


On Wednesday, August 31, 2022 at 5:13:17 PM UTC+2 chr...@gmail.com wrote:

> 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* tbp1...@gmail.com <https://groups.google.com/>*!* 
>
>
> On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 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 chr...@gmail.com 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 tbp1...@gmail.com 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 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:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>

Re: newbie stuck

[chr...@gmail.com]

I believe there is no schema or DTD, unfortunately. You could ask why at 
the github link I posted just before (and deleted and re-edited several 
times!)
During my many test of Windows outliners, I remember that one interpreted 
an OmniOutliner column (each headline can have columns), which was also 
present in the OmniOutliner-output OPML file. The column was interpreted as 
an extra attribute of the headline (or maybe a "sub-attribute", if there's 
such a thing in XML?)
Strangely, the Windows program showed it ABOVE each headline (maybe because 
of alphabetical sorting, because the headline column was call "Topic" and 
the second column "Description"), slightly offset to the right, and it was 
editable. So, of course, it would be great if the content of the body pane 
could pass into the OPML file! I hope OmniOutliner would show it as a 
column, but having not read the whole OPML 2.0 spec, I don't know how that 
works. I'm willing to reinstall all those dodgy Windows "outliners" to test 
this, if you want.

On Wednesday, August 31, 2022 at 5:06:53 PM UTC+2 tbp1...@gmail.com wrote:

> Here is Dave (Winer)'s spec <http://opml.org/spec2.opml>.  I would think 
> that there would be an XML schema (or maybe a DTD would be able to the the 
> joib) somewhere that could be used for validating an OPML file, but I 
> didn't find one in a very hasty search.
>
> Since OPML only includes what Leo calls headline text, I'm wondering if 
> there would ever be any use for text in (Leo) node bodies.  An OPML outline 
> node can contain other information besides the headline text, so maybe 
> that's why the plugin may deal with Leo's user attributes - the info has to 
> go somewhere.  
>
> Is it the case, @chr, that you want to round-trip OPML files with other 
> applications with full fidelity (except maybe data about an editor's 
> state)?  Or do you only need to include a subset of information?
>
>
>
> On Wednesday, August 31, 2022 at 10:13:37 AM UTC-4 chr...@gmail.com wrote:
>
>> I found only one public one at http://validator.opml.org/ (website and 
>> validator by Dave Winer, the original OPML guy, still at the wheel), but it 
>> doesn't seem to work so well.
>> I submitted an issue at 
>> https://github.com/scripting/opml.org/issues/6#issue-1357384900
>>
>>
>> On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 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 chr...@gmail.com 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 tbp1...@gmail.com 
>>>> 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 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.

Re: newbie stuck

[chr...@gmail.com]

 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* tbp1...@gmail.com <https://groups.google.com/>*!* 


On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 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 chr...@gmail.com 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 tbp1...@gmail.com 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 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 
>>>> callAltXFunctionfunc(event)  File 
>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 346, in 
>>>> writeOpmlCommandc.opmlCommands.writeFile(fileName)  File 
>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 319, in 
>>>> writeFileok = 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/d8f27a6c-b9d7-4d28-9004-1882257735e6n%40googlegroups.com.

Re: newbie stuck

[chr...@gmail.com]

 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* tbp1...@gmail.com <https://groups.google.com/>*!* 


On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 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 chr...@gmail.com 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 tbp1...@gmail.com 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 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 
>>>> callAltXFunctionfunc(event)  File 
>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 346, in 
>>>> writeOpmlCommandc.opmlCommands.writeFile(fileName)  File 
>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 319, in 
>>>> writeFileok = 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/11e07d79-b872-4bbd-9ca9-1eae703773bdn%40googlegroups.com.

Re: newbie stuck

[chr...@gmail.com]

 Dave Winer the man himself validated my file on his OPML validator, so it 
works just fine. I recommend
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 
for questions and issues with fixing Leo OPML output, always keeping in 
mind that it is an EXCHANGE FORMAT, and that less is more.

*Thanks* tbp1...@gmail.com <https://groups.google.com/>! 


On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 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 chr...@gmail.com 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 tbp1...@gmail.com 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 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 
>>>> callAltXFunctionfunc(event)  File 
>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 346, in 
>>>> writeOpmlCommandc.opmlCommands.writeFile(fileName)  File 
>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 319, in 
>>>> writeFileok = 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/a6df75a5-f291-432e-9b8a-8b9971b1271an%40googlegroups.com.

Re: newbie stuck

[chr...@gmail.com]

Dave Winer the man himself validated my file on his OPML validator, so it 
works just fine. I recommend
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 
for questions and issues with fixing leoOPML.py, always keeping in mind 
that it is an EXCHANGE FORMAT, and that less is more.

Thanks tbp1...@gmail.com! 

On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 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 chr...@gmail.com 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 tbp1...@gmail.com 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 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 
>>>> callAltXFunctionfunc(event)  File 
>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 346, in 
>>>> writeOpmlCommandc.opmlCommands.writeFile(fileName)  File 
>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 319, in 
>>>> writeFileok = 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/ad6378d3-548d-4592-86d9-05aa68511514n%40googlegroups.com.

Re: newbie stuck

[chr...@gmail.com]

 I found only one public one at http://validator.opml.org/ (website and 
validator by Dave Winer, the original OPML guy, still at the wheel), but it 
doesn't seem to work so well.
I submitted an issue at 
https://github.com/scripting/opml.org/issues/6#issue-1357384900


On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 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 chr...@gmail.com 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 tbp1...@gmail.com 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 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 
>>>> callAltXFunctionfunc(event)  File 
>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 346, in 
>>>> writeOpmlCommandc.opmlCommands.writeFile(fileName)  File 
>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 319, in 
>>>> writeFileok = 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/fd59fc72-85bb-49e3-bd53-6b1f6bb545f4n%40googlegroups.com.

Re: newbie stuck

[chr...@gmail.com]

I found only one public one at http://validator.opml.org/ (website and 
validator by Dave Winer, the original OPML guy, still at the wheel), but it 
doesn't seem to work so well.
I submitted an issue at https://github.com/scripting/opml.org/issues/

On Tuesday, August 30, 2022 at 6:18:50 PM UTC+2 tbp1...@gmail.com 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 chr...@gmail.com 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 tbp1...@gmail.com 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 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 
>>>> callAltXFunctionfunc(event)  File 
>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 346, in 
>>>> writeOpmlCommandc.opmlCommands.writeFile(fileName)  File 
>>>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 319, in 
>>>> writeFileok = 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/5c457597-db9b-493b-8df9-c7f1a0776c3cn%40googlegroups.com.

Re: newbie stuck

[chr...@gmail.com]

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 tbp1...@gmail.com 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 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 
>> callAltXFunctionfunc(event)  File 
>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 346, in 
>> writeOpmlCommandc.opmlCommands.writeFile(fileName)  File 
>> "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 319, in 
>> writeFileok = 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/f52b1903-5c90-4e26-9536-3408e82e1426n%40googlegroups.com.

Re: Newbie stuck - new traceback, "OPML" file attached

[chr...@gmail.com]

Well, it's not really "what I want", but what should be, because, again, 
OPML is an outline exchange format.

With the command "read-opml-file", Leo imports just fine the 
iPhone-generated "Document.opml" file I attached previously here. Why can't 
it export it back in the same format  with "write-opml-file" so that I can 
edit it further on the phone? 

The Leo OPML file should be standard so that it could be transmitted back 
and forth and edited by any Windows, Mac, Linux , IOS, and Android 
OPML-aware app/program, then returned to Leo for further editing. 
I'm talking about only the basic text outline, which is what OPML is about: 
even clones should be changed into copies before conversion to .opml. A 
script in Leo could rebuild the cloning after re-import, I guess.
There are many such OPML-capable apps/programs, disk-based or cloud-based: 
other outliners, mind-mappers, note-takers, to-do listers, task managers, 
workflow managers, converters, dozens of RSS/Atom feed aggregators and 
readers, etc. This back -and-forth editing is impossible with the .opml 
produced by Leo. If it's not OPML, don''t call it OPML.

Scripting .leo or .leojs conversion to true .opml is fine, but impossible 
on an IOS or Android device because of apps sandboxing. 

My usage case: Brainstorming, note-taking, project developpment, writing.
I have a sync folder on all my Windows, macOS, IOS, and Android devices at 
home, where I work. Outside the home, I carry my iPhone and iPad mini.
With an OPML-compliant Leo, I could create a text-only outline about some 
project, save it as .opml in the sync folder of my PC. It would get 
instantly synced to all the other devices. When I go to a meeting or get an 
email while away, I want to integrate the email text or the meeting notes 
into the outline, on my iPhone or iPad. The changed outline is 
automatically transmitted via 5G, and when I get home, I could open it in 
OPML-compliant Leo, and continue working on it.
This is now possible with OmniOutliner, but only on Apple devices, and most 
of my workflow is organized around 30 years of Windows use, with complex 
programs I know like the back of my hand, utilities, batch scripts, 
registry hacks etc. That is why I need an outline editor on Windows, and 
why I need OPML, which is the only universal outline file format that can 
be opened, modified and saved, when the spec (http://opml.org/spec2.opml) 
is respected. 

Very good cloud solutions exist, but just read this: 
https://workflowy.com/privacy-policy/ and you'll understand why I want a 
fully private setup.

Chris

P.S. I'm also considering using Leo as a PIM/scrapbook, but that wouldn't 
require OPML. 
On Tuesday, August 30, 2022 at 4:43:10 AM UTC+2 tbp1...@gmail.com wrote:

> Would you explain what you would like to happen?  Do you want to get a Leo 
> outline with the nodes named and indented according to the OPML file?  If 
> so, that should be pretty easy to write a script for even without a plugin 
> (in case it's too hard to get it functioning).
>
> On Monday, August 29, 2022 at 8:29:55 PM UTC-4 chr...@gmail.com wrote:
>
>> Hello Edward,
>>
>> Well, since my original message has now appeared in the group page, I'll 
>> repost only the relevant part, just in case. I also attached here an OPML 
>> file done in 5 minutes with OmniOutliner (THE outliner reference, I dare 
>> say) on my iPhone and saved as OPML. That's the basic format that will 
>> allow Leo to exchange files with any other correctly designed 
>> OPML-compatible app/program. It's an old spec, but it now is the way for 
>> compatibility of outlines with mobile devices as well.
>>
>> Other attributes can be added, but since OPML is first and foremost an 
>> outline exchange format, Vnodes and Tnodes won't cut it.  You can find the 
>> spec at
>> http://opml.org/spec2.opml . Jump straight to the paragraph titled 
>> "Text Attributes".
>>
>> You can also look at the source of that webpage and see that between 
>> lines 49 and 438, it is indeed pure OPML, which is compatible with Mozilla 
>> Firefox and Thunderbird (OPML is used a lot for passing RSS feeds), 
>> Microsoft Edge, and most probably Google Chrome too (never used it). The 
>> outline on that webpage is two levels deeps, and the divots work in the 
>> browser.
>>
>> Now my original post is made a bit obsolete by the second one -the extra 
>> keyword args on lines 321 and 322 of leoOPML.py are not compatible with 
>> c.fileCommands.write_Leo_file() - but here it is again:
>>
>> 
>> *Problem*
>> I'm pretty sure I got the leoOPML.py plugin configuration right (file, 
>> tree, directives, body panel), bu

Re: Newbie stuck - new traceback, "OPML" file attached

[chr...@gmail.com]

Hello Edward,

Well, since my original message has now appeared in the group page, I'll 
repost only the relevant part, just in case. I also attached here an OPML 
file done in 5 minutes with OmniOutliner (THE outliner reference, I dare 
say) on my iPhone and saved as OPML. That's the basic format that will 
allow Leo to exchange files with any other correctly designed 
OPML-compatible app/program. It's an old spec, but it now is the way for 
compatibility of outlines with mobile devices as well.

Other attributes can be added, but since OPML is first and foremost an 
outline exchange format, Vnodes and Tnodes won't cut it.  You can find the 
spec at
http://opml.org/spec2.opml . Jump straight to the paragraph titled 
"Text Attributes".

You can also look at the source of that webpage and see that between lines 
49 and 438, it is indeed pure OPML, which is compatible with Mozilla 
Firefox and Thunderbird (OPML is used a lot for passing RSS feeds), 
Microsoft Edge, and most probably Google Chrome too (never used it). The 
outline on that webpage is two levels deeps, and the divots work in the 
browser.

Now my original post is made a bit obsolete by the second one -the extra 
keyword args on lines 321 and 322 of leoOPML.py are not compatible with 
c.fileCommands.write_Leo_file() - but here it is again:

*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 
callAltXFunctionfunc(event)  File 
"C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 346, in 
writeOpmlCommandc.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'*
 every time, 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
See attachment
On Tuesday, August 30, 2022 at 12:21:26 AM UTC+2 Edward K. Ream wrote:

> On Mon, Aug 29, 2022 at 5:15 PM chr...@gmail.com  wrote:
>
>> I haven't seen my first message in the list yet, the forum is probably 
>> moderated...
>> Further tests editing the guilty function call:
>>
>
> I approved both messages, but I only see this one.
>
> Leo opens leo_test1.opml when I change .opml to .leo.
>
> Please resend your original message. Thanks.
>
> Edward
>

-- 
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/78e438c8-3fe4-48b4-b005-faf7e2229607n%40googlegroups.com.


  
My Document
0,3,4,7,8,9,12,13,14

0
0
682
684
  
  

  
  


  

  
  


  
  



  

  

  

  
  


  

Newbie stuck - new traceback, "OPML" file attached

[chr...@gmail.com]

I haven't seen my first message in the list yet, the forum is probably 
moderated...
Further tests editing the guilty function call:




* File "C:\Python310\lib\site-packages\leo\plugins\leoOPML.py", line 319, 
in writeFileok = self.c.fileCommands.write_Leo_file(fileName, 
1)TypeError: FileCommands.write_Leo_file() takes 2 positional arguments but 
3 were given*

So it works with the fileName only, but the result is not an OPML file, not 
even XML (see attachment).

-- 
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/d2cfa374-c4ec-4fde-b1a2-d385a0d5a115n%40googlegroups.com.


http://leoeditor.com/namespaces/leo-python-editor/1.1; >





newHeadline 1
newHeadline 1.1
newHeadline 1.2

newHeadline 2
newHeadline2.1

newHeadline 3