>
> To make it safer use a different ~/.leo for each one by changing HOME
>> environment variable before starting Leo.
>>
>
> *This is counter intuitive to my understanding of why Python has
> introduced PyVE's!*
>
> At the moment my gut feeling is that Leo should change here ...
>
It becomes a question of how isloated and unique one wishes to become. The
leakage you described is from settings and files in your HOME directory
being available to all PyVEs. Extend virtualness far enough, so there's
zero chance of one environment seeping into another, you're better using
different computer login accounts, or even distinct OS and hardware.
I can envisage configuring Leo so that if {current-Leo-install-path}
doesn't match {HOME/.leo-recorded-install-path}: create a new
{HOME/.leo-install-path}, but then you'd lose all your settings and be back
to factory defaults. From there it might be desirable to have a Leo user
settings migration tool, but how to choose what to keep and what to leave
behind? Every person will have their own and different answers.
Getting back to the warning messages you saw: they mean the files you had
open in previous session are not available now. There's nothing else Leo
could possibly do other than say "hey, I can't find these". Well, actually
it could just never save and reload sessions; maybe there's even a setting
for that already.
-matt
-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 view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/a4bf1826-9636-49ad-88ea-3f9332308f92%40googlegroups.com.
