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 diffe
On Wed, Apr 19, 2023 at 9:04 AM Thomas Passin 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
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
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 g
I do this from time to time. It's a bit weird that it only works with the
tree panel, but I guess that's not a problem.
On Wednesday, April 19, 2023 at 1:06:36 PM UTC-4 jkn wrote:
> I have been meaning to check this for ages - what happens if you try to
> drag and drop a .leo file into a runni
