Re: Dropping a file vs importing it: @edit vs @auto
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 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 tbp1...@gmail.com 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 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 @ 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/174f0919-517e-452d-b584-fc92a881e758n%40googlegroups.com.
Re: Dropping a file vs importing it: @edit vs @auto
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 tbp1...@gmail.com 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 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 @ 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/a8249f47-f8d7-4b71-9283-4f99e95c8005n%40googlegroups.com.
Re: Dropping a file vs importing it: @edit vs @auto
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 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 @ 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/bfb47d9b-3f36-4d26-a77d-814730362df8n%40googlegroups.com.
Re: Dropping a file vs importing it: @edit vs @auto
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, 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 @ 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS24U9-XOxx882Rmqz7zXb%2Ba9%3DL9mPgPm%3DEOucgeyEHprw%40mail.gmail.com.
Dropping a file vs importing it: @edit vs @auto
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? -- 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/a4e59c7d-2176-4f7a-80ea-11ffb74d656en%40googlegroups.com.
Re: Impressive ChatGPT responses
On Tue, Apr 18, 2023 at 6:42 PM Thomas Passin wrote: ...I am not sure I am ever going to write code completely by hand again! > And I expect these tools to get better fast." Thanks for this quote. I wouldn't dispute it. My prediction: some time in the future AI's will program in their own non-text language, a language that *might* be back-translatable into a text language that we humans can read. AI's will also use their own IDEs, which again *might* have a human analog. Python's, Leo's, and vs-code's days are numbered. 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/CAMF8tS3heg9Fyx7iUkUnRkt2JRS7ayZQ7-Ti54PJEapc8ReYnQ%40mail.gmail.com.
