Windows filename handling is utterly broken.
paul-lalonde opened this issue · 5 comments
Edwood (nor acme) cannot handle driver letters and backwards slashes in path names.
I believe we use Path internally in some places to handle paths, but not everywhere. We should probably use package path everywhere we parse paths/guess at filenames. Button 3/Look would benefit greatly. This would almost make edwood usable on Windows.
That code needs some more attention. More refactoring. Maybe I'll have time soon.
Meta comment: the tag contents are both editable text and "structured" in that Edwood parses the tag. This is special cased throughout the code in convoluted ways. My design intuition is that the "right way" to address this is to provide some kind of parse tree layer adjacent to a file.Buffer
.
I can't yet decide if I want to make fixing this contingent on refactoring the handling of "structured" text in Edwood.
@paul-lalonde given that I don't have a windows device conveniently at hand, are there some low-road concrete fixes that might be the 20% that addresses 80% of your unhappiness?
Fixed in #485