There may simple way forward for Bob Hossley, one that prevents gnx 
conflicts before they happen.  When spawning a host of .leo files, the 
process spawning that host would invoke each instance of Leo with 
--leo-id=<a unique string>.  This would solve the problem at the source.

*Background*

Back in 2014 we attempted to fix #35 
<https://github.com/leo-editor/leo-editor/issues/35> (gnx conflicts) with a 
post pass.  I'm not sure there *is* a post pass, although I would have 
sworn it was in leoFileCommands.py.  This post pass is a form of damage 
limitation.

I allowed myself to be convinced that gnx conflicts were inevitable. The 
argument went like this:  Terry's brother shares his leoID, and so gnx 
clashes could not be prevented.

But do we really need to worry about gnx conflicts? gnx conflicts can only 
happen if *two* conditions are met:

1. Two people (or instances of Leo) share the same leoID, the first 
component of every gnx that they create.
2. Two people (or instances of Leo) share the same .leo file!

I regret not pushing back on the notion that gnx conflicts are serious 
concerns.  Indeed, sharing .leo files from strangers is asking for 
trouble.  You should only accept a .leo file from someone you trust.  But 
in that case, it should be easy to ensure that your leoID is different from 
the person with whom you share .leo files! Terry and his brother should 
just choose different leoID's!

So Bob could prevent gnx clashes by ensuring that each instance of Leo runs 
with a different leoID.  Thus the --leo-id option. 

*Summary*

gnx clashes can only happen when sharing .leo files with someone who *also* 
shares your leoID.

Imo, Bob's woes stem from an extreme form of such sharing.  His test 
environment pushes Leo beyond reasonable design limits. 

Rather than remediate almost intractable problems within Leo itself, a 
--leo-id command-line argument would ensure that all separate copies of Leo 
generate unique gnx's.  When spawning a host of .leo files, the process 
spawning that host would invoke each instance of Leo with unique strings S 
in --leo-id=S.

Your comments, please.

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/dbaa0456-dd2a-4c3b-93d7-5bca30f180d2%40googlegroups.com.

Reply via email to