Would you like to have a copy of the LEO file that contains the repository? 
You could see you my set-up. 

On Saturday, February 27, 2021 at 11:47:19 AM UTC-5 Edward K. Ream wrote:

> On Thu, Feb 25, 2021 at 11:30 PM David Szent-Györgyi <[email protected]> 
> wrote:
>
>> Leo is your project, you provide free access to the fruits of your labor, 
>> if you're going to remote @root that's your decision, but it may cause me 
>> to ask questions I need answered if I am to preserve access to work that 
>> I've done. 
>>
>
> Please ask any questions you like.
>
> My question is this: what can you do with @root that is difficult or 
> clumsy with @file? Can you provide an example of how you use @root?
>
> I've written about my use of Leo 4.3: it served as an easily deployed tool 
>> for building utilities in the form of Windows Script Host files (WSF 
>> files), and that I came up with a scheme that made it easy for me to use a 
>> LEO file to hold the source code for the library of routines (in JScript or 
>> VBScript) used by the WSF files as well as the source code for the 
>> utilities I was building. Since each WSF file was independent and had to 
>> include every library routine used therein, the libraries ended up written 
>> to disk in multiple places in the various WSF files. 
>>
>
> OK.
>
> These days, WSF files are frowned up on because script kiddies and other 
>> malefactors used VBScript and similar technologies, so perhaps I shouldn't 
>> care about preserving the ones I wrote, but I still use some of them 
>> in-house, and they need maintenance; I don't want to lose access to my 
>> Leo-based development environment if I can help it. 
>>
>
> I'm not here to judge what people should be doing with Leo!
>
>> The last thing I would want to do would be cut myself off from Leo's 
>> vibrant community; I am still a lone developer, working without help to 
>> write utilities for work when I'm short of time for work as it is. That 
>> said, if I must give up on using future versions of Leo, what do I do: pick 
>> a version of Leo that is closest to my needs and create a fork? 
>>
>
> Don't worry. Your objection will suffice to have Leo support @root 
> indefinitely.  If you don't mind, I'll add your name to the comments in 
> leoTangle.py, to tell me, and future Leo devs, who's using this feature.
>
> 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/d2fe2977-3742-4175-8b07-89097882a10fn%40googlegroups.com.

Reply via email to