Hi Thomas, I must have erased those long names on floppy disks from my memory! I remember the path stuff going in a config file and I remember editing that file with CyngusEd. And yes absolutely, yes - Felix deserves some sort of medal - well a gold medal for his work on this. Just brilliant... as is Leo itself. I've been trying to get my sons on board for ever but one is a hard core C guy and the other uses Jupiter Notebooks. Which I know nothing about, except that it's a big deal in Python world. Anyway thanks again Thomas and keep up the good work! IH
On Wednesday, 30 August 2023 at 13:06:42 UTC+1 tbp1...@gmail.com wrote: > On Wednesday, August 30, 2023 at 7:36:12 AM UTC-4 Israel Hands wrote: > > Thomas I'm reading your note about modules and paths - I feel I need to > understand this better to make headway. > > > The expression to use with the *-m* flag is the same one you would use to > import a module. In the *leoserver* example, you would expect to import > the module with *import leo.core.leoserver*. So that's what you put after > the *-m* on the command line: *leo.core.leoserver*. There may be a few > exceptions for some more esoteric import constructs, but you probably will > never have to worry about them. > > > I have to say I found path setting on the Amiga more intuitive, those were > the days. > > > Except when we had to type out those sometimes long names of the floppy > disk the file was on - remember those? > > Again many thanks for taking the time, LeoInteg is a thing of beauty! IH > > > A fantastic job by Felix, isn't it? > -- 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/d050ad22-a141-4be4-ba9e-66263a89424an%40googlegroups.com.
