... But when I start it Viktor's way the restart-leo command opens the
pip-installed version. IOW
cd ~/git/leo-editor
python3 -m leo.core.runLeo
leads to restarting the pip-installed version instead of the git.leo-editor
version. I have found out the difference, though not yet why the difference
happens. When you start Leo in the git/leo-editor directory, you can
display the Python path be running this in Leo's console tab:
import sys
print('\n'.join(sys.path))
This will show that the first location on the search path is git/leo-editor,
as it should be.
When you restart it and the wrong version opens, the first location on my
system is git/leo-editor/leo/core. Of course, Python won't find
leo.core.runLeo there so it looks in site-packages instead and finds the
pip-installed version.
So, progress.
On Saturday, October 12, 2024 at 1:30:58 PM UTC-4 Thomas Passin wrote:
> I have just confirmed that the restart-leo command does work on my
> OpenSUSE VM. Leo is not being run in a venv on this one. I use the same
> launch command as I posted above except it doesn't open a venv. This is
> with a recent version of devel (yesterday's).
>
>
>
> On Saturday, October 12, 2024 at 12:26:24 PM UTC-4 Edward K. Ream wrote:
>
>> On Sat, Oct 12, 2024 at 7:04 AM Viktor Ransmayr <[email protected]>
>> wrote:
>>
>> > I knew that this command restarts Leo - but - I was not sure which
>> use-cases it supports ...
>>
>> As you imply, restart-leo should "just work." However, there may be
>> platform-dependent limitations.
>>
>> I will consider PRs that remove such limitations, but everything works
>> for me on Windows.
>>
>> 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/51e8d4ac-955b-4cc1-ba1b-60fc78c0295an%40googlegroups.com.
