https://bugs.documentfoundation.org/show_bug.cgi?id=157820
Bug ID: 157820
Summary: Command line argument does not accept Windows \\?\
path prefix
Product: LibreOffice
Version: 7.3.4.2 release
Hardware: All
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: LibreOffice
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: bwech...@yahoo.com
Description:
I have used Libre Calc on Windows 11 as the default app for opening .csv files
for some while. Out of the blue, it stopped working.
I looked the command up in the Windows registry and tried to duplicate it in a
PowerShell using the path that a right-click>Copy as path gets me from the
Windows explorer. Turns out, the file path was prepended with \\?\. Running
Calc with that as an argument sees Calc end silently and do nothing. If I
remove this prefix, Calc opens the CSV file and all is good.
Turns out this prefix is used (as is \\?\UNC\) by the Windows API when paths
are longer than some erstwhile path length limit to flag to users that it's a
long one.
Alas, LibreOffice is unaware of the convention. No surprise there. But given
any cross-platform app has to accommodate filesystem idiosyncrasies across
those systems. And it seems this is any easy thing to accommodate and arguably
should for smooth cross-platform functioning (i.e helping me overcome internal
resistance to using LibreOffice here - but alas it is simply way better than
excel in so many subtle ways I am always drawn to it).
Steps to Reproduce:
1. Try top open a file in LibreOffice from the command line by using a long
path that Windows Copy as path provides with a \\?\ prefix.
2. Try again, removing that prefix.
Actual Results:
The file is not opened.
Expected Results:
The file opens.
Reproducible: Always
User Profile Reset: No
Additional Info:
I clearly don't have the latest version, but am constrained to use portable
versions (thanks to PortableApps). I will see if they have a later one and be
back and close this if it happens to be fixed of course. Opted for file first
as I searched Bugzilla for "\\?\" and found nothing so I doubt this has ever
been spotted to be honest. It arises only with very long paths. I don't know
the exact length, but the one I'm using has 278 chars so I imagine this prefix
kicks in at 256 and longer.
--
You are receiving this mail because:
You are the assignee for the bug.
