Big list of software that cannot handle spaces or accents in paths
-
@raceprouk I've learned that Visual Studio's crash recovery doesn't work on solutions with a space in their path. If it crashes with a solution in, say
C:\Source code
, loaded the attempt to auto restart fails with "could not find the file or directory C:\Source"
-
@grunnen said in Big list of software that cannot handle spaces or accents in paths:
Now try to make this work in a whitespace-proof way:
$ rm `tar -tf archive.tar`
tar -tf ../test.tar |sort -r|while read f; do rm "$f" || rmdir "$f"; done
works for everything but deliberate nastiness like filenames consisting of only spaces which are not listed with a backslash before the space at least by GNU tar (I'm too lazy to test any others), which I think is a bug because names containing spaces are listed correctly.
Tabs … yeah. Tabs break pretty much everything. Even your eyesight uponls
. I don't even want to know about vertical space or zero-width non-joiners.
-
@laoc Unfortunately some trawling of manpages suggests neither GNU tar nor GNU cpio apply their --null option to printed file lists.
-
IMO It would be better if non-alphanumeric characters weren't allowed in filenames. It made everything more annoying to code for pretty much no benefit.
-
@pleegwat said in Big list of software that cannot handle spaces or accents in paths:
Unfortunately some trawling of manpages suggests neither GNU tar nor GNU cpio apply their --null option to printed file lists.
Wait, you wanted conceptual consistency?!
-
@wharrgarbl said in Big list of software that cannot handle spaces or accents in paths:
IMO It would be better if non-alphanumeric characters weren't allowed in filenames.
Whose alphabet? Whose numbers?
-
@dkf ASCII or die
-
@pleegwat said in Big list of software that cannot handle spaces or accents in paths:
@laoc Unfortunately some trawling of manpages suggests neither GNU tar nor GNU cpio apply their --null option to printed file lists.
Definitely. No idea why they can't produce it when the fact that they can consume it suggests someone understood the utility of this format.
@wharrgarbl said in Big list of software that cannot handle spaces or accents in paths:
IMO It would be better if non-alphanumeric characters weren't allowed in filenames. It made everything more annoying to code for pretty much no benefit.
Não.
^ would that be considered "alphabetic"?
-
@laoc No, but we got adapted to ASCII for years before these different incompatible encoding madness started.
-
@wharrgarbl Who's "we"? Japan and Russia didn't. They had their own encoding.
-
@blakeyrat ASCII is good enough for the C language that is the only one that matters
-
@wharrgarbl EBCDIC was good enough for C too, especially with some trigraphs to help out!
-
@dkf "was"?
-
@greybeard said in Big list of software that cannot handle spaces or accents in paths:
@dkf "was"?
That's what I keep hoping, yes…
-
@wharrgarbl said in Big list of software that cannot handle spaces or accents in paths:
IMO It would be better if non-alphanumeric characters weren't allowed in filenames. It made everything more annoying to code for pretty much no benefit.
You need at least hyphens. Parentheses are nice to have, as are commas, periods and slashes. In English, apostrophes are important. Semicolons, square brackets and the odd plus sign are also useful.
I occasionally long for question marks and colons.
-
How could I forget the ampersand? The percent sign? The dollar sign? The pound sign? The at sign?
Probably best to start black listing characters at this point. And guess what, that's how it works today.
-
@zecc said in Big list of software that cannot handle spaces or accents in paths:
How could I forget the ampersand? The percent sign? The dollar sign? The pound sign? The at sign?
Probably best to start black listing characters at this point. And guess what, that's how it works today.
Yeah, but Windows' choice of what to blacklist is rather inconvenient.
-
@zecc said in Big list of software that cannot handle spaces or accents in paths:
You need at least hyphens.
No, I don't.
-
@dreikin said in Big list of software that cannot handle spaces or accents in paths:
@zecc said in Big list of software that cannot handle spaces or accents in paths:
How could I forget the ampersand? The percent sign? The dollar sign? The pound sign? The at sign?
Probably best to start black listing characters at this point. And guess what, that's how it works today.
Yeah, but Windows' choice of what to blacklist is rather inconvenient.
It'd be great if every Windows instance added an extra randomly selected Unicode character to that list.
-
@tsaukpaetra said in Big list of software that cannot handle spaces or accents in paths:
Side note, in a potential move to get themselves off of this list, Epic is doing a thing!
http://coconutlizard.co.uk/blog/ue4/solongmaxpath/
Oh wait, that's just file name path... Well, shoot. Looks like they're still on it! :D
That website fucks with my scrolling so I am unable to read it.
-
@ben_lubar said in Big list of software that cannot handle spaces or accents in paths:
website
@ben_lubar said in Big list of software that cannot handle spaces or accents in paths:
read
-
@wharrgarbl said in Big list of software that cannot handle spaces or accents in paths:
@zecc said in Big list of software that cannot handle spaces or accents in paths:
You need at least hyphens.
No, I don't.
I see you don't generate files with ISO-8601 dates in their filenames.
-
@zecc said in Big list of software that cannot handle spaces or accents in paths:
I see you don't generate files with ISO-8601 dates in their filenames.
Just use the number of seconds from the start of the Unix epoch instead. Easy!
-
@dkf said in Big list of software that cannot handle spaces or accents in paths:
@zecc said in Big list of software that cannot handle spaces or accents in paths:
I see you don't generate files with ISO-8601 dates in their filenames.
Just use the number of seconds from the start of the Unix epoch instead. Easy!
.... Shutup....
-
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
Russia didn't
Don't know about Japan, but Russia at least has Volapuk
-
@wharrgarbl said in Big list of software that cannot handle spaces or accents in paths:
IMO It would be better if non-alphanumeric characters weren't allowed in filenames. It made everything more annoying to code for pretty much no benefit.
Yeah fuck users.
-
@zecc said in Big list of software that cannot handle spaces or accents in paths:
The pound sign?
Do you mean
#
or£
? Because the latter is outside ASCII and is as useful as$
for normal people in some countries.
-
@zemm said in Big list of software that cannot handle spaces or accents in paths:
@zecc said in Big list of software that cannot handle spaces or accents in paths:
The pound sign?
Do you mean
#
or£
? Because the latter is outside ASCII and is as useful as$
for normal people insomenormal countries.FTFY
-
@wharrgarbl said in Big list of software that cannot handle spaces or accents in paths:
IMO It would be better if non-alphanumeric characters weren't allowed in filenames. It made everything more annoying to code for pretty much no benefit.
IMO just banning control characters would be sufficient, and then you could use ASCII properly and use some of those for record separators, leaving space for display.
I found a filename with a tab in it the other day, would have been done through FileZilla or similar.
And a separate directory was "duplicated" in an
ls
. Highlighting revealed that each duplicate had a space appended. I don't even...
-
@zemm said in Big list of software that cannot handle spaces or accents in paths:
@wharrgarbl said in Big list of software that cannot handle spaces or accents in paths:
IMO It would be better if non-alphanumeric characters weren't allowed in filenames. It made everything more annoying to code for pretty much no benefit.
IMO just banning control characters would be sufficient, and then you could use ASCII properly and use some of those for record separators, leaving space for display.
I found a filename with a tab in it the other day, would have been done through FileZilla or similar.
And a separate directory was "duplicated" in an
ls
. Highlighting revealed that each duplicate had a space appended. I don't even...Be glad it wasn't done with a carriage return!
-
Firefox (fixed)
-
@marczellm Some “fun” things linked off there…
Yep, someone wasn't handing user-specified data to the DB safely…
-
LibreOffice (fixed in upcoming 6.0 release)
-
AmiDuOS - Android emulator by American Megatrends
-
The OCaml programming language (fixed)
-
@marczellm Interesting reason for that - its due to a Windows API that makes it almost impossible to do the right thing (you tell it how many bytes to write, it tells you how many graphemes it wrote - so you don't know when its time to stop)
-
@gwowen said in Big list of software that cannot handle spaces or accents in paths:
@marczellm Interesting reason for that - its due to a Windows API that makes it almost impossible to do the right thing (you tell it how many bytes to write, it tells you how many graphemes it wrote - so you don't know when its time to stop)
I'm liking the Linux method of "it's just a string of bytes. you don't need to assume anything about it." more and more every day.
-
@ben_lubar said in Big list of software that cannot handle spaces or accents in paths:
I'm liking the Linux method of "it's just a string of bytes. you don't need to assume anything about it." more and more every day.
There's much to be said for that, even though it does involve the complexity on the reader side that you might have to deal with a part-written high-level codepoint/grapheme.
-
@ben_lubar said in Big list of software that cannot handle spaces or accents in paths:
I'm liking the Linux method of "it's just a string of bytes. you don't need to assume anything about it." more and more every day.
I liked it from the start. Policy does not belong to the kernel is a good rule.
@dkf said in Big list of software that cannot handle spaces or accents in paths:
There's much to be said for that, even though it does involve the complexity on the reader side that you might have to deal with a part-written high-level codepoint/grapheme.
The more opinionated systems won't save you most of that complexity anyway.
-
@bulb said in Big list of software that cannot handle spaces or accents in paths:
Policy does not belong to the kernel is a good rule.
It gets messy when people insist on having case-insensitive filesystems, since filesystems are basically things that need to tangle into the kernel (for good reason) yet case-insensitivity is a policy decision as it requires decisions to be made as to whether two filenames are talking about the same thing. Making the kernel work with byte-for-byte comparisons only is far simpler; user-level code can provide a case-insensitive layer (and also do whatever normalisation is required/desired) in the GUI but the kernel sticks with “are these bit sequences identical?”.
-
@dkf If only it were just case insensitivity. Users can sometimes be convinced the "file.txt" and "File.txt" aren't the same file - it's a lot more difficult to explain why "Dave's MP3s" and "Dave’s MP3s" aren't the same folder.
-
Tkinter
-
@marczellm That sounds like something has misdetected the keyboard, and that's got to be before it gets to tkinter as I know enough about the internals of that to know that it'd just be passing around the characters. It literally doesn't reinterpret anything. (Or if it is doing so, it's in the Python layer; the underlying graphics toolkit is happy with all of those characters in so far as I can test as I don't have a Hungarian keyboard.)
-
@dkf said in Big list of software that cannot handle spaces or accents in paths:
I don't have a Hungarian keyboard.
Switching keyboard layouts (probably with an on-screen keyboard active so you can tell what’s where) should be sufficient to test it.
-
@dkf thanks for the tip. Indeed I have two language settings on this PC, and it looks like tkinter (or the layers above/below) are not considering the keyboard but the language setting.
-
@marczellm said in Big list of software that cannot handle spaces or accents in paths:
Indeed I have two language settings on this PC, and it looks like tkinter (or the layers above/below) are not considering the keyboard but the language setting.
Oh! Did you switch keyboard layout after launching the process?
[EDIT] And that's it. It's a bug that the Tk library doesn't respond to
WM_INPUTLANGCHANGEREQUEST
events.
-
@dkf said in Big list of software that cannot handle spaces or accents in paths:
@marczellm said in Big list of software that cannot handle spaces or accents in paths:
Indeed I have two language settings on this PC, and it looks like tkinter (or the layers above/below) are not considering the keyboard but the language setting.
Oh! Did you switch keyboard layout after launching the process?
[EDIT] And that's it. It's a bug that the Tk library doesn't respond to
WM_INPUTLANGCHANGEREQUEST
events.But it does! If I switch the input language (not the keyboard layout, as you can see that remains the same) when the Tkinter window is open, the issue disappears and I can now type ő and ű. Also you cannot get the old wrong behaviour back after this.
-
@marczellm said in Big list of software that cannot handle spaces or accents in paths:
But it does! If I switch the input language (not the keyboard layout, as you can see that remains the same) when the Tkinter window is open, the issue disappears and I can now type ő and ű. Also you cannot get the old wrong behaviour back after this.
Ugh, so I wasn't quite right; it responds to
WM_INPUTLANGCHANGE
, but it ignores thelParam
in the message. It does track language changes, which is expressed in thewParam
, but that's not what you need.Bug report filed for you.
-
@dkf said in Big list of software that cannot handle spaces or accents in paths:
Bug report filed for you.
Thanks! Is it related to this one?
-
@marczellm said in Big list of software that cannot handle spaces or accents in paths:
@dkf said in Big list of software that cannot handle spaces or accents in paths:
Bug report filed for you.
Thanks! Is it related to this one?
Ooh, and a case of Bug Obsoleted By Rewrite Still Present: