On Mon, 7 Nov 2011 03:55:15 -0800 (PST) "Edward K. Ream" <[email protected]> wrote:
> On Nov 4, 3:03 am, "Edward K. Ream" <[email protected]> wrote: > > > Obviously, the difference between N:\whatever and \N:whatever is hard > > to see, but I think it's pretty clear that one works and the other > > doesn't, quite independently of Leo. > > Apparently, much the same discussion appears at this bug: > > unable to describe root directory on thumb drive > https://bugs.launchpad.net/leo-editor/+bug/613153 > > I've just promoted this bug to high priority so it will be resolved > asap. Part of the problem, as mentioned in the thread for that bug, is http://bugs.python.org/issue1669539 which has escaped resolution for 4 years as is listed as impacting py 3.3. I think, before trying to fix this, we should have a page in the docs. which painstakingly spells out how paths are determined, and then just implement whatever the page says. Which I think means *not* using os.getcwd() which is basically random. I think our past consensus was the concept of "process current directory" makes sense in an interactive shell, but for Leo the correct context is "node current directory", determined by the effects of all path related aspects of all parent nodes. Of course unix has no analog of windows "A:" being the current directory on the the "A:" drive vs. "A:\" being the root of the "A:" drive, so ultimately that part's Window's specific. Also, we should handle shares specified as //machine/share/path/file.leo or \\machine\share\path\file.leo. Without confusing them with unix absolute paths. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
