Re: Unifying leoPy.leo and leoPlugins.leo is a big win

[Edward K. Ream]

On Saturday, October 17, 2020 at 3:22:44 PM UTC-5, Edward K. Ream wrote:

> I'll create a new command that only calls c.fileCommands.save_ref().

Per #1716 , 
LeoPyRef.leo now contains @button write-leoPyRef, a specialized rewrite of 
fc.save_ref():

- It can only be run from leoPy.leo, and always writes to LeoPyRef.leo.
- It writes only a given list of nodes,  ['Startup', 'Notes', 'Code'], 
thereby eliminating the need for a sentinel node.

I think this specialization makes sense. In any case, I am happily using it.

Please let's not argue about this. It's my preference. 

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/d37ddb32-f144-4cdc-a168-0fb7baa2d5c9o%40googlegroups.com.

Re: Unifying leoPy.leo and leoPlugins.leo is a big win

[vitalije]

On Saturday, October 17, 2020 at 10:22:44 PM UTC+2, Edward K. Ream wrote:
>
>
>
> On Sat, Oct 17, 2020 at 7:30 AM vitalije > 
> wrote:
>
> I think you should really try using public/private outline scheme. 
>>
>
> Thanks for the reminder. I'm not sure I always want ctrl-s to save to both 
> outlines. Instead, I'll create a new command that only calls c.
> fileCommands.save_ref(). 
>
> I use it in my LeoPy.leo and it was never an issue. If all my work is done 
in the private zone, git never showed LeoPyRef.leo changed. 
Vitalije

-- 
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/bc68dccb-aa3b-40d4-8d5b-006e13f83817o%40googlegroups.com.

Re: Unifying leoPy.leo and leoPlugins.leo is a big win

[Edward K. Ream]

On Sat, Oct 17, 2020 at 7:30 AM vitalije  wrote:

I think you should really try using public/private outline scheme.
>

Thanks for the reminder. I'm not sure I always want ctrl-s to save to both
outlines. Instead, I'll create a new command that only calls c.fileCommands.
save_ref().

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/CAMF8tS1a7TxOUGH%2BOng%2BvBUPG05A%3DNpT_AOR6Shz5ZNwG%2BnBmw%40mail.gmail.com.

Re: Unifying leoPy.leo and leoPlugins.leo is a big win

[vitalije]

>
> Similarly, the open-leo-py-ref-leo command makes it significantly easier 
> to keep LeoPyRef.leo in sync with my personal leoPy.leo files. It may sound 
> like a small matter, but it isn't. 


I think you should really try using public/private outline scheme. Just to 
remind you of this rather hidden Leo feature.

If an outline has a top level node with the headline 
`---begin-private-area---`, then this node is separating the public part of 
the outline (before this node) and the private part of the outline (after 
this node). The first line of this node should have a path to the public 
(shared) Leo document.

Now when you execute c.fileCommands.save_ref() command, the public part is 
saved in the shared Leo document. In my private Leo documents I always have 
a node with headline `@button n-save @key=Ctrl-s` and the body line always 
contains at least these two lines:

c.save()
c.fileCommands.save_ref()

That way my public or reference Leo files never get out of sync.

When I pull changes from the others, I have to remember to execute 
`read-ref-file` which updates public part of the outline from the reference 
file.

Vitalije

>

-- 
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/db3be5ac-30a6-47bf-8d61-fda94cc272b6o%40googlegroups.com.

Unifying leoPy.leo and leoPlugins.leo is a big win

[Edward K. Ream]

Now that I have done so, I regret not doing it years ago. I had been taking 
consul of nameless fears. In fact, every aspect of Leo's development has 
been simplified:

- Clones naturally span both plugins and Leo's core. The clone-find and 
git-diff commands work much better.
- I now use a unified "Recent Code" organizer, and that has had happy 
effects in organizing my to-do lists and lists of completed items.

Similarly, the open-leo-py-ref-leo command makes it significantly easier to 
keep LeoPyRef.leo in sync with my personal leoPy.leo files. It may sound 
like a small matter, but it isn't.

*Summary*

So-called "little" improvements can sometimes be very important. Not 
everything is an earthquake like the clone-find commands :-)

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/2e32a2f5-1f7c-4260-9d85-7c00d3ee95d5o%40googlegroups.com.