Need Leo files, revision control, and collaboration refresher

[Matt Wilkie]

Hi Folks,

I'm getting back into Leo after some time away and need a refresher on how
to best structure my files and folders, particularly with how to work with
source code version control systems and other collaborators who don't use
Leo.

My old workbooks are filled with broken @path references and I want to
ensure this go 'round doesn't lead to the same end! As I study the pattern
of brokenness, most stem from me keeping my .leo files outside of the
version controlled repos. This is a kindness to collaborators, no need for
them to be subjected to a stream of commit noise when I'm just muttering to
myself.

The table of contents  doesn't help
direct my quest ("Leo with other programs" would be a good place for a
future doc of this type) . Where should I start?

Thanks!

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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Need Leo files, revision control, and collaboration refresher

[Matt Wilkie]

Found what I was looking for,
http://leoeditor.com/FAQ.html#leo-in-shared-environments. Does anyone have
other tips along the same lines to share?


On Sat, Oct 21, 2017 at 1:07 PM, Matt Wilkie  wrote:

> Hi Folks,
>
> I'm getting back into Leo after some time away and need a refresher on how
> to best structure my files and folders, particularly with how to work with
> source code version control systems and other collaborators who don't use
> Leo.
>
> My old workbooks are filled with broken @path references and I want to
> ensure this go 'round doesn't lead to the same end! As I study the pattern
> of brokenness, most stem from me keeping my .leo files outside of the
> version controlled repos. This is a kindness to collaborators, no need for
> them to be subjected to a stream of commit noise when I'm just muttering to
> myself.
>
> The table of contents  doesn't help
> direct my quest ("Leo with other programs" would be a good place for a
> future doc of this type) . Where should I start?
>
> Thanks!
>
> 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 leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Need Leo files, revision control, and collaboration refresher

[Edward K. Ream]

On Sat, Oct 21, 2017 at 6:12 PM, Matt Wilkie  wrote:

> Found what I was looking for, http://leoeditor.com/FAQ.html#
> leo-in-shared-environments. Does anyone have other tips along the same
> lines to share?
>

​Caching can sometimes cause problems, especially when switching between
git branches.  To see if you have been bitten, ​do write-at-file-nodes
(Ctrl-Shift-W).  They should remain unchanged after load.  If not,
physically delete all caches and redo the tests.  I think there may be
subtle bugs lurking somewhere.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Need Leo files, revision control, and collaboration refresher

[Edward K. Ream]

On Sunday, October 22, 2017 at 10:42:09 AM UTC-5, Edward K. Ream wrote:

​Caching can sometimes cause problems, especially when switching between 
> git branches.  To see if you have been bitten, ​do write-at-file-nodes 
> (Ctrl-Shift-W).  They should remain unchanged after load.  If not, 
> physically delete all caches and redo the tests.  I think there may be 
> subtle bugs lurking somewhere.
>

Yesterday I discovered, or perhaps rediscovered, a problem that isn't a 
bug, can't be "solved", but nevertheless can be disconcerting.

Private copies of LeoPyRef.leo, that is, leoPy.leo, are "global".  That is, 
they persist *unchanged* when switching branches.  In effect, they act like 
(sometimes) unwanted caches.

Here's what happened yesterday.  After switching away from master to 
another branch, I (inadvertently) sorted the children of the g.Debugging 
node. Oops!

After that, switching back to master is going to create a change to 
leoGlobals.py which is unrelated to caching.  There is no easy way to 
"undo" this change using leoPy.leo.   A leo-centric diff will reveal that 
the change is harmless, just a rearrangement of nodes.  However, this will 
not be so obvious using git diff.

If, somehow, one realizes what is going on, then one could undo the change 
using LeoPyRef.leo, assuming *it* is in sync with leoPy.leo, but that isn't 
likely.

The main lesson are:

1. Use leo-centric diffs (leo --diff) when mysteries happen.
2. Don't make unnecessary structural changes in leoPy.leo when in branches 
other than master.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Need Leo files, revision control, and collaboration refresher

[Matt Wilkie]

Thank you for these thoughts, they're helpful

-- 
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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Re: Need Leo files, revision control, and collaboration refresher

[Edward K. Ream]

On Mon, Oct 30, 2017 at 7:35 AM, Matt Wilkie  wrote:

Thank you for these thoughts, they're helpful
>

​You're welcome.  I've update the FAQ in LeoDocs.leo, but not yet on the
web.

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 post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.