I have been meaning to check this for ages - what happens if you try to
drag and drop a .leo file into a running leo?
looks like you have to drop it into the tree pane, and it then becomes one
of the open .leo files - cool
and if you try to drag and drop a non-leo file (into the tree pane) it gets
turned into an @file node.
Good, I think...
J^n
On Wednesday, April 19, 2023 at 4:38:58 PM UTC+1 [email protected] wrote:
> Well, it's not *too* mysterious. When you drop the file its path gets
> added to the command line that the OS uses to launch Leo (or whatever
> program the desktop icon is for).
>
> On Wednesday, April 19, 2023 at 10:43:49 AM UTC-4 Edward K. Ream wrote:
>
>> On Wed, Apr 19, 2023 at 9:04 AM Thomas Passin <[email protected]> wrote:
>>
>> If there is a Leo shortcut on the desktop and you drag and drop a non-Leo
>>> file on it, an instance of Leo will start and contain an @edit node for the
>>> dropped file (a .cmd file will be put into an @file node).
>>>
>>> If you import the same file, it will get imported into an @auto subtree.
>>>
>>> Why the difference, and shouldn't both ways do the same thing?
>>>
>>
>> Heh. I didn't know that I could drag and drop as you describe. Here are
>> some other ways of importing files:
>>
>> - The import-file command calls *c.importAnyFile*. This method contains
>> various special cases. Maybe some of those cases are dubious.
>> - Create an empty @<file> node and do *refresh-from-disk*.
>> - Create an @button node to do exactly as you please with
>> *c.recursiveImport.*
>>
>> I don't think consistency between these ways is all that important.
>>
>> 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/a8249f47-f8d7-4b71-9283-4f99e95c8005n%40googlegroups.com.
