Since your python installation got completely broken, you will have to specify the one that works. So first, try to run it:
jam$ python3.6 -m pip list This will show you if Leo is already installed for python 3.6, and what version. Pip may not be installed for this version yet. On some linux systems you have to have your package manager install it. Once you get pip installed, then do jam$ python3.6 -m pip install leo Or, if leo is already installed for python3.6 (and it's not Leo v6.3), upgrade it: jam$ python3.6 -m pip install --upgrade leo Once installed, invoke it: jam$ python3.6 -m leo.core.runLeo It may seem clumsy, using all those python3.6 -m ... commands, but it will make sure that you install Leo and invoke it using the correct working python installation. If python3.6 isn't working, then you first need to get some version of python3.x installed and working, along with pip. Then proceed as I have outlined. Good luck! Let us know how it turns out. On Wednesday, December 16, 2020 at 8:28:54 PM UTC-5 andyjim wrote: > Tom, you have saved my bacon. .leoRecentFiles found the missing file, 7 > directories deep at usr/local/lib/python3.7/site-packages/Leo/doc/. The > file appears uncorrupted, but it seems to be the only copy of that file > anywhere on the system. I have made another copy now. And python3.7 is > present, although I think python3.9 supplanted it when I installed it. > Doesn 't matter I guess, as presumably Leo and Python will find each other. > > Now to reinstall Leo and implement a sensible strategy with leo files. > Here's what I get with pip install leo: > > jam$ pip install leo > > Traceback (most recent call last): File "/Users/jam/anaconda2/bin/pip", > line 7, in <module> from pip.*internal.main import main ImportError: No > module named pip.*internal.main > > Where do I go from here? Thanks. > > > On Tuesday, December 15, 2020 at 12:16:24 AM UTC-5 [email protected] > wrote: > >> The most obvious thing would be that you never saved it, just kept it >> open in Leo since March. But that seems pretty far-fetched. So let's hope >> that the correct .leo file has another name! I tend to hit Save when I >> have an idle moment. I also keep a USB backup drive connected all the >> time, and backup my work directories to it fairly often. Less commonly, I >> sometimes put a .leo file in my on-disk Mercurial repository (which is >> Windows only, so far as I know). But that doesn't always do the job, >> especially when much of the work is in @file trees. >> >> Also, I wouldn't be keeping my .leo files in ~/.leo, since that is >> written to by Leo and who knows what might happen to it sometime if Leo or >> an Leo installer burps. What I usually do these days is to create a new >> .leo file in a project tree I'm working on. Then I symlink all those .leo >> files to a standard directory, like (for linux) ~/leo_outlines. This >> way, I don't have to remember where all my .leo files are, since I can just >> go to the leo_outlines directory to find them. >> >> I realize that none of these musings will help you right now. But going >> forward once you recover, maybe they might help. >> >> If it were me, I'd search my whole drive for .leo files first, and then >> grep through them later. It would save a lot of time: >> >> find / -name *.leo -type f 2>/dev/null # or find ~ ... >> >> Also, if you can get Leo reinstalled, the file might show up on the >> recent files list - and you might recognize the file name there. Actually, >> maybe the recent file list is still there and uncorrupted: >> >> ~/.leo/.leoRecentFiles.txt >> >> Good luck! >> >> >> On Monday, December 14, 2020 at 10:50:17 PM UTC-5 andyjim wrote: >> >>> no, my files were/are in Users/jam/.leo There are a few .leo files >>> there, but the only one that might be it (the primary file I wrote in since >>> March) has only March entries in it. Confusing. Mac Finder says it was >>> created, last modified and last opened at 7:39pm on March 31. Seems >>> strange. I stopped paying attention to the name of the file, Leo just >>> opened it every day and I continued writing in it, not thinking about the >>> name, so I cannot be certain the March 31 file I find is it, but if so, >>> it's somehow lost all data since March 31. Other leo system files in that >>> directory are dated 12-12-2020, which is the day this happened, so that >>> appears to be the active leo directory at the time. >>> My focus now is on finding that file. It's more important than what >>> went wrong. I currently have a grep search going for a text phrase that I >>> know is in the file (but can be in several others as well) Been going for >>> several hours only on the Users/jam directory. It has so far found seven >>> files containing the phrase, none of which contain the lost data. >>> Could the March 31 file have gotten corrupted, fragmented? If so, it >>> seems I should still be able to find the raw data on the drive. I lost an >>> important file five years ago, on Windows at the time, and was fortunate >>> enough to locate the data on the drive with a specialized data finding >>> program. Anyone know of a good one for Mac? I'll see if I can find that >>> program again but don't know if it works on Mac. >>> On Monday, December 14, 2020 at 7:47:10 AM UTC-5 Edward K. Ream wrote: >>> >>>> On Sun, Dec 13, 2020 at 7:08 PM [email protected] <[email protected]> >>>> wrote: >>>> >>>>> Your actual .leo files are probably still there, where ever they were >>>>> before. You could look for them with find. Then after getting Leo >>>>> reinstalled, you should be good to go. >>>>> >>>> >>>> I agree. You didn't store .leo files in usr/local/opt did you? >>>> >>>> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/e6e3088c-1036-4ce9-bd57-4c760f7bbc30n%40googlegroups.com.
