On Sun, Jun 26, 2016 at 5:52 PM, Edward K. Ream <[email protected]> wrote:
> On Sun, Jun 26, 2016 at 6:44 PM, 'Terry Brown' via leo-editor
> <[email protected]> wrote:
>>
>> On Sun, 26 Jun 2016 03:14:26 -0700 (PDT)
>> Mike Hodson <[email protected]> wrote:
>>
>> > I would like to be able to copy a single .leo file somewhere, and
>> > then have any related 'real files' (for lack of better term) be
>> > re-created out of content already contained within the .leo file be
>> > re-created upon import or something of this nature.
>
>
> The official terminology for what you are calling "real" files is "external"
> files.
>
Gotcha.
> Thanks, Terry, for you reply. I agree that @clean or @nosent will work.
>
>
> No need to do a script. You can simply select a tree of @clean/@nosent
> nodes and do
> write-at-file-nodes (Shift-Ctrl-W) to force the writing/creation of external
> files.
>
> So if all your @clean (or @nosent) nodes are children of a single root node,
> you can simply select that node and do Shift-Ctrl-W.
>
So for an example, if I created a single root node called "my script
and its modules" and then underneath it, the nodes then correspond to
the individual files I write to make the project work, then i
transport only the leo file, at which point I right click on the 'my
script and its modules' node, then write files to disk, I'll end up
with all the individual source files to make the application work,
created via the .leo file.
I'll definitely look further into the @nosent node type. This does
sound like what I would be doing, running an overarching Leo session
concurrent with its inbuilt 'edit in external editor' feature to call
something like Subline3 or perhaps even Visual Studio Code. While I do
see the potential need to modify a file externally to the ability to
run Leo, such as in a ssh session somewhere that has no X or python
libraries installed, almost always this remote situation would be
pushed to by the local, more fully outfitted with software,
development system.
>
> Alternatively, you can write a script that selects that root node and then
> does c.k.simulateCommand('write-at-file-nodes').
If I didn't feel that a simple single action by myself was fine, I'd
probably explore this option more. Perhaps at some point in the future
:)
> HTH. Please feel free to ask more questions.
> Edward
It did indeed! I'll continue digging through the rabbit's tunnels and
asking more as I go.
Thanks!
Mike
--
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
