https://bugs.documentfoundation.org/show_bug.cgi?id=157820
--- Comment #8 from Bernd Wechner <[email protected]> --- (In reply to Federico Gallo from comment #6) > I actually don't know if Libreoffice provide the dialog or just call the > file explorer (that seems to be the right thing to do nowadays at least on > linux). I'm not even using Windows. > You don't have to provide that information if you don't want to, I'm not the > person that will work on this I think you misunderstand the bug. I am using LibreOffice on the command line. I am not using the File Open dialog. I did a quick test and long paths (over 256 chars) open fine with Open File dialog box. Not a problem. But when you try and open one on the command line as follows say: CD MyVeryDeepLongDIr "E:\Util\LibreOffice\LibreOfficeCalcPortable.exe" MyFIle then LibreOffice pops up: E:\Util\LibreOffice\Wideband freq response - ByRegionsAll - Sv nonAvg - upward-facing transducer_transposed.CSV does not exist. A totally bizarre thing to report. And if I try it with the full path as delivered by the Explorer when I right-click and rhen click Copy as path, then LibreOffice does nothing at all. The copied path (and so the one that Open With is passed also by the explorer is prepended with "\\?\". If I remove that, and try again, LibreOffice starts and loads the file. Summary: File Open dialog box is all good Receiving paths from the command line is broken for long paths (>256 chars) because of a prefix Windows provides to the path to indicate it is long, but which is not understood by whatever method LibreOffice subsequently tries to open same file. -- You are receiving this mail because: You are the assignee for the bug.
