> P.S. All these picky details illustrate just how difficult it is to write proper installation instructions. Imo, it's the most difficult documentation there is.
agreed! Regarding http://leoeditor.com/installing.html#creating-windows-file-associations: Is this on Launchpad? "LeoDocs.leo > Users Guide > Basics > Installing Leo" is not the same. (I'm wondering if it would be more efficient to just suggest edits in place.) (1) Is there a reason "--gui=qttabs" is used in Method 1 and not #2? Is it even necessary? On my machine there is no obvious difference between: python launchLeo.py and python launchLeo.py --giu=qttabs (3) These command need to have admin privileges, so *"Open an elevated<http://windows.microsoft.com/en-ca/windows7/command-prompt-frequently-asked-questions>Windows console (command prompt), then type:" * And the `ftype` example is missing trailing `"%1"` or `"%1" %*` As for the second syntax, that is the association the Python installer (2.7) creates. I don't know what the extra `%*` does. In any case, both of them enable double-clicking on a .leo file in Windows Explorer. Without them Leo starts but doesn't open the selected .leo file. So complete line: ftype LeoFile="<path to python>\pythonw.exe" "<path to launchLeo.py>\launchLeo.py" "%1" %* (4) Strike any mention of creating a batch files here. They aren't needed for *association*. The extra info here could be folded into "Running Leo > Windows" section. -matt -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
