Big list of software that cannot handle spaces or accents in paths
-
My Windows username is Márton. That drives software crazy. This thread documents that.
-
(fixed)Error (initialization): User M rton has no home directory Warning (initialization): An error occurred while loading ‘nil’: File error: Opening directory, No such file or directory, c:/Users/M\341rton/AppData/Roaming
-
from tensorflow.contrib.rnn.python.ops.gru_ops import * Traceback (most recent call last): ... File "C:\Users\Márton\ProgrammingStuff\virtualenv\lib\site-packages\tensorflow\python\framework\load_library.py", line 64, in load_op_library None, None, error_msg, error_code) tensorflow.python.framework.errors_impl.NotFoundError: D:\Marci\Programozás\algorimp\test\venv\lib\site-packages\tensorflow\contrib\rnn\python\ops\_gru_ops.dll not found
-
I'm seeing a lot of gnus in here. That appears to be a recurring theme.
I recall hearing at one point that the reason Microsoft created the "Program Files" folder as the default location for installed programs was specifically to force developers to write software that could properly handle spaces in paths.
-
Theano
(fixed)Problem occurred during compilation with the command line below: D:\msys2\mingw64\bin\g++.exe -shared -g -O3 -fno-math-errno -Wno-unused-label -Wno-unused-variable -Wno-write-strings -D_hypot=hypot -march=haswell -mmmx -mno-3dnow -msse -msse2 -msse3 -mssse3 -mno-sse4a -mcx16 -msahf -mmovbe -maes -mno-sha -mpclmul -mpopcnt -mabm -mno-lwp -mfma -mno-fma4 -mno-xop -mbmi -mbmi2 -mno-tbm -mavx -mavx2 -msse4.2 -msse4.1 -mlzcnt -mno-rtm -mno-hle -mrdrnd -mf16c -mfsgsbase -mno-rdseed -mno-prfchw -mno-adx -mfxsr -mxsave -mxsaveopt -mno-avx512f -mno-avx512er -mno-avx512cd -mno-avx512pf -mno-prefetchwt1 -mno-clflushopt -mno-xsavec -mno-xsaves -mno-avx512dq -mno-avx512bw -mno-avx512vl -mno-avx512ifma -mno-avx512vbmi -mno-clwb -mno-pcommit -mno-mwaitx -mno-clzero -mno-pku --param l1-cache-size=32 --param l1-cache-line-size=64 --param l2-cache-size=6144 -mtune=haswell -DNPY_NO_DEPRECATED_API=NPY_1_7_API_VERSION -m64 -DMS_WIN64 -ID:\Python35\lib\site-packages\numpy\core\include -ID:\Python35\include -ID:\Python35\lib\site-packages\theano\gof -o C:\Users\Márton\AppData\Local\Theano\compiledir_Windows-10-10.0.14393-SP0-Intel64_Family_6_Model_60_Stepping_3_GenuineIntel-3.5.2-64\tmpf0hafy5j\m0cee5d6551f2e027b5d68bb77d6b83a4.pyd C:\Users\Márton\AppData\Local\Theano\compiledir_Windows-10-10.0.14393-SP0-Intel64_Family_6_Model_60_Stepping_3_GenuineIntel-3.5.2-64\tmpf0hafy5j\mod.cpp -LD:\Python35\libs -LD:\Python35 -lpython35 ERROR (theano.gof.opt): Traceback (most recent call last): ... File "D:\Python35\lib\site-packages\theano\compat\__init__.py", line 42, in decode return x.decode() UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe1 in position 10: invalid continuation byte
-
@masonwheeler said in Big list of software that cannot handle spaces or accents in paths:
I recall hearing at one point that the reason Microsoft created the "Program Files" folder as the default location for installed programs was specifically to force developers to write software that could properly handle spaces in paths.
Which spawned a whole separate world of problems when a bunch of idiots hardcoded
C:\Program Files\
or other named paths in their applications, breaking localization and causing bitness compatibility issues.
-
Fun fact, Google Drive has almost no limitations on names for files and folders. You can even use double quotes and slashes (both kinds). When synced to a computer, it just replaces illegal characters with underscores. Basically, there's no such thing as a "path" in Google Drive.
@Groaner said in Big list of software that cannot handle spaces or accents in paths:
@masonwheeler said in Big list of software that cannot handle spaces or accents in paths:
I recall hearing at one point that the reason Microsoft created the "Program Files" folder as the default location for installed programs was specifically to force developers to write software that could properly handle spaces in paths.
Which spawned a whole separate world of problems when a bunch of idiots hardcoded
C:\Program Files\
or other named paths in their applications, breaking localization and causing bitness compatibility issues.That would have happened regardless of the name, wouldn't it've?
-
@Groaner said in Big list of software that cannot handle spaces or accents in paths:
bunch of idiots
Well, they do keep the rest of us gainfully employed...
-
XAMPP is a particulary bad offender. First of all it does ask for UAC permission. Then you get this:
Then this:
Then if I install to 'D:\Program Files (x86) - because it did warn about C:\Program Files (x86) not being OK - it starts installing fine, then you get this right before the end:
Quoting the official website:
The XAMPP open source package has been set up to be incredibly easy to install and to use.
Quoting https://community.apachefriends.org/f/viewtopic.php?f=16&t=75766]
It is not planned to support that on XAMPP.
-
(fixed)
(using cache: C:/Users/Márton/AppData/Local/MiKTeX/2.9/luatex-cache/generic) Sorry, but lualatex did not succeed. The log file hopefully contains the information to get MiKTeX going again: C:/Users/Márton/AppData/Local/MiKTeX/2.9/miktex/log/lualatex.log FATAL lualatex - MultiByteToWideChar() did not succeed; last error code is 1113
-
SyncTeX
-
@masonwheeler said in Big list of software that cannot handle spaces or accents in paths:
I'm seeing a lot of gnus in here. That appears to be a recurring theme.
I recall hearing at one point that the reason Microsoft created the "Program Files" folder as the default location for installed programs was specifically to force developers to write software that could properly handle spaces in paths.
Which I assume is why Qt and some drivers like to unpack/install into C:\ instead of somewhere sensible.
-
If I were you, I'll just give up and use whatever 8.3 format filename displayed by running "dir /x".
-
@marczellm said in Big list of software that cannot handle spaces or accents in paths:
XAMPP is a particulary bad offender. First of all it does ask for UAC permission. Then you get this:
Then this:
Then if I install to 'D:\Program Files (x86) - because it did warn about C:\Program Files (x86) not being OK - it starts installing fine, then you get this right before the end:
Quoting the official website:
The XAMPP open source package has been set up to be incredibly easy to install and to use.
Quoting https://community.apachefriends.org/f/viewtopic.php?f=16&t=75766]
It is not planned to support that on XAMPP.
Same thread:
These single components are programmed primarily on and for *nix based systems and because of that are sometimes only able to work on *nix friendly path names.
*nix is far more permissive than Windows. Any valid Windows path is a valid *nix path (at least on the most common variety: linux).
marczellm wrote:
But at least sensible error messages should indicate these problems to the user!
No. Its a question of your personal knowledge that (especially) servers do not accept all characters in file names. It is very well known that specials characters are not supported. Apache is designed to run on different OS and different file systems, its an sophisticated Administrators task to install and configure a webserver. It is not designed for everybody.
See, this kind of shit is why @blakeyrat hates open source projects. It's also why it's hard to disagree with him a lot of the time. This is wrong, wrong-headed, and talking down to the user for making an eminently reasonable request. Good job, Altrea and Nobbie.
-
@Dreikin said in Big list of software that cannot handle spaces or accents in paths:
See, this kind of shit is why @blakeyrat hates open source projects
What people miss is that I don't hate open source projects because they are open source, but because projects run by assholes like this are open source projects 100% of the time. It's not cause, it's correlation.
What I don't get is why dickhole there typed that long paragraph instead of just typing "fuck you", which is obviously what he was trying to communicate.
EDIT: seriously, marczellm, go back in that forum and reply to that post with:
"Point me to something in the Linux or POSIX specification or API contract that says the user can't install software into a folder named 'Program Files'."
And watch the fucker squirm, because there is nothing and he is a fucking piece of shit you should call out, not simply because he's a piece of shit, but because he's objectively wrong on this point. Then tell him you knew there wasn't because a guy who hates Linux with a passion knows way more about Linux than he does.
If I didn't have to sign up for an account, I'd post that shit right now.
-
@masonwheeler said in Big list of software that cannot handle spaces or accents in paths:
I recall hearing at one point that the reason Microsoft created the "Program Files" folder as the default location for installed programs was specifically to force developers to write software that could properly handle spaces in paths.
And another team at Microsoft created a short name "PROGRA~1", which has neither spaces nor more than 8 characters.
-
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
@Dreikin said in Big list of software that cannot handle spaces or accents in paths:
See, this kind of shit is why @blakeyrat hates open source projects
What people miss is that I don't hate open source projects because they are open source, but because projects run by assholes like this are open source projects 100% of the time. It's not cause, it's correlation.
You also seem to think it's impossible for Open Source project to not be run by assholes, which is what people disagree with you about.
-
@Gąska said in Big list of software that cannot handle spaces or accents in paths:
You also seem to think it's impossible for Open Source project to not be run by assholes,
That's a lie. I've actually had pleasant interactions with a few open source projects, although the negative interactions far outweigh them.
It's just the default.
-
@blakeyrat well, you sure made it look like much more than just the default. Like that time when you said MS is going to die in response to .Net going partially open source.
-
@masonwheeler said in Big list of software that cannot handle spaces or accents in paths:
I'm seeing a lot of gnus in here. That appears to be a recurring theme.
I recall hearing at one point that the reason Microsoft created the "Program Files" folder as the default location for installed programs was specifically to force developers to write software that could properly handle spaces in paths.
All the major operating systems have allowed spaces in file and directory names for more than 20 years, and yet, there is still a lot of software that shits itself when it encounters a directory with a space in the name.
How is that even possible?
-
TRWTF is cp1250.
Have you tried EBCDIC?
-
@Gąska said in Big list of software that cannot handle spaces or accents in paths:
well, you sure made it look like much more than just the default.
I'm confused. Are you upset that he doesn't troll consistently and if he's made one hyperbolic statement once he should not later present a reasonable position? I mean, what response are you going for, to get him to confess that he actually hasn't ever had a positive interaction with an open source project?
@El_Heffe said in Big list of software that cannot handle spaces or accents in paths:
How is that even possible?
When your idea of inter-process communication is to use the command line to pass information between programs, the fact that command lines split tokens on whitespace presents problems that shitty programmers don't care to address. Yes, you can escape those, but then you wouldn't be a shitty programmer and wouldn't be using the command line in the first place.
-
Browsing through my C:\ drive:
Both of those were for building Qt, which also can't handle spaces.
Note: The install path must not contain any spaces or Windows specific file system characters.
-
@Kian said in Big list of software that cannot handle spaces or accents in paths:
@Gąska said in Big list of software that cannot handle spaces or accents in paths:
well, you sure made it look like much more than just the default.
I'm confused. Are you upset that he doesn't troll consistently and if he's made one hyperbolic statement once he should not later present a reasonable position?
There's a difference between a single hyperbolic statement and a decade of one hyperbolic statement after another.
-
@masonwheeler said in Big list of software that cannot handle spaces or accents in paths:
I'm seeing a lot of gnus in here.
I know a GNU developer who even defended the fact that GNU Make cannot handle spaces properly. In his opinion, file systems that allow spaces are . GNU developers are… special.
-
Oh, and IIRC, the Android SDK can be added to this list. I'm pretty sure some of the scripts broke the last time I unpacked it in Program Files.
-
@marczellm This is fucking terrible. Why even bother to make a Windows program of you're not going to follow any of Windows' conventions?
-
I should make a collection of the mail (including snail mail) that I get from various agencies, from my own country where accents are integral part of the language, with the accent in my name botched up.
Usually I get called Rã©mi (or something similar), sometimes R=E9mi, and I got recently RU+00E9mi, which was a new one.
-
@El_Heffe said in Big list of software that cannot handle spaces or accents in paths:
All the major operating systems have allowed spaces in file and directory names for more than 20 years,
Yes, but GNU programmers live 40 years in the past.
-
@Gąska said in Big list of software that cannot handle spaces or accents in paths:
@masonwheeler said in Big list of software that cannot handle spaces or accents in paths:
I recall hearing at one point that the reason Microsoft created the "Program Files" folder as the default location for installed programs was specifically to force developers to write software that could properly handle spaces in paths.
And another team at Microsoft created a short name "PROGRA~1", which has neither spaces nor more than 8 characters.
That's for compatibility with DOS*, which couldn't handle spaces, or names longer than 8 characters.
*Early versions; later versions may have gained support?
-
@Kian said in Big list of software that cannot handle spaces or accents in paths:
but then you wouldn't be a shitty programmer
Yes.
and wouldn't be using the command line in the first place
No. ;)
-
@blakeyrat said in Big list of software that cannot handle spaces or accents in paths:
EDIT: seriously, marczellm, go back in that forum and reply to that post with:
"Point me to something in the Linux or POSIX specification or API contract that says the user can't install software into a folder named 'Program Files'."
And watch the fucker squirm, because there is nothing and he is a fucking piece of shit you should call out, not simply because he's a piece of shit, but because he's objectively wrong on this point. Then tell him you knew there wasn't because a guy who hates Linux with a passion knows way more about Linux than he does.
If I didn't have to sign up for an account, I'd post that shit right now.I was bored so signed up for an account and posted that, but it requires moderator approval so probably won't ever see the light of day
-
@El_Heffe said in Big list of software that cannot handle spaces or accents in paths:
All the major operating systems have allowed spaces in file and directory names for more than 20 years, and yet, there is still a lot of software that shits itself when it encounters a directory with a space in the name.
How is that even possible?
Because, even though the UNIX file system has supported spaces for decades, you can still screw up too easily, e.g. with bad shell scripts:
$ touch "Program Files" $ find * Program Files $ for x in `find *`; do ls $x; done ls: Access to Program denied: File not found ls: Access to Files denied: File not found $
Edit: Which means that UNIX users still get an itchy feeling with file names containing whitespace and don't use them, which in turn means that UNIX developers can get away with not supporting it.
Edit2: This particular case has in fact been solved by the GNU people:
$ find * -print0 | xargs -0 ls Program Files $
But it is nonstandard and probably isn't possible with other utilities than "find".
-
@marczellm said in Big list of software that cannot handle spaces or accents in paths:
Quoting https://community.apachefriends.org/f/viewtopic.php?f=16&t=75766]
It is not planned to support that on XAMPP.
translated:
We are of Linux. What are these "spaces" you keep talking about? Have you tried rm -rf ? It must be PEBKAC.
-
@Dreikin said in Big list of software that cannot handle spaces or accents in paths:
the most common variety: linux
I would have thought OS X (macOS these days) is more common than Linux, at least when looking at desktop and laptop computers where problems like this are more likely to occur than on servers (because sysadmins probably figure they’ll need to avoid accents etc. even when they don’t), let alone phones.
Incidentally, what bugs me about OS X’s filenames is not that there’s an illegal character (the colon) but that it doesn’t tell you which character is the problem when you use it. Now, I know to avoid colons, but I suspect many people trying a filename like
Holiday 2017: Hà Nội.mp4
might not.
-
@anonymous234 said in Big list of software that cannot handle spaces or accents in paths:
Why even bother to make a Windows program of you're not going to follow any of Windows' conventions?
Cross-platform software? In my experience, it tends to either stick to the conventions of one OS and apply them to all the others it gets built for, or stick to whatever original ideas the designer has — typically making it hard to use on all systems.
-
@asdf said in Big list of software that cannot handle spaces or accents in paths:
@masonwheeler said in Big list of software that cannot handle spaces or accents in paths:
I'm seeing a lot of gnus in here.
I know a GNU developer who even defended the fact that GNU Make cannot handle spaces properly. In his opinion, file systems that allow spaces are . GNU developers are… special.
Wait! So this guy thinks we should all use FAT16 or FAT12 without VFAT support?
-
@Gurth said in Big list of software that cannot handle spaces or accents in paths:
@anonymous234 said in Big list of software that cannot handle spaces or accents in paths:
Why even bother to make a Windows program of you're not going to follow any of Windows' conventions?
Cross-platform software? In my experience, it tends to either stick to the conventions of one OS and apply them to all the others it gets built for, or stick to whatever original ideas the designer has — typically making it hard to use on all systems.
For maximum cross-platform wankery, consider Blender, which for a long time (which might not have ended) has its own File|Open dialog box. OK, there are ways to customise the Win32/Win64 box, but that's not what they did. They built their own from scratch, and it supports a lot of things, including spaces in pathnames and filenames.
But one thing it doesn't support is UNC paths. You have to map a drive letter to \\server\share and use that drive letter. But it doesn't have a button to do that mapping, so you have to go to Explorer or the command line or something and do it.
-
@asdf said in Big list of software that cannot handle spaces or accents in paths:
Oh, and IIRC, the Android SDK can be added to this list. I'm pretty sure some of the scripts broke the last time I unpacked it in Program Files.
Android SDK's installer refuses to use a target path with spaces.
And yet, when it's installed by Visual Studio it is installed inside Program Files just fine. :person_of_undefined_gender_shrugging:
-
@Zecc said in Big list of software that cannot handle spaces or accents in paths:
Android SDK's installer
That one doesn't even seem to exist anymore. The only standalone download I could find the last time I looked was an archive.
And yet, when it's installed by Visual Studio it is installed inside Program Files just fine.
Should be fine if you use Visual Studio, because it probably doesn't use the command-line tools in the SDK.
-
@RaceProUK said in Big list of software that cannot handle spaces or accents in paths:
@Gąska said in Big list of software that cannot handle spaces or accents in paths:
And another team at Microsoft created a short name "PROGRA~1", which has neither spaces nor more than 8 characters.
That's for compatibility with DOS*, which couldn't handle spaces, or names longer than 8 characters.
*Early versions; later versions may have gained support?
The limitation was imposed by FAT, not by DOS.
-
@PJH said in Big list of software that cannot handle spaces or accents in paths:
@RaceProUK said in Big list of software that cannot handle spaces or accents in paths:
@Gąska said in Big list of software that cannot handle spaces or accents in paths:
And another team at Microsoft created a short name "PROGRA~1", which has neither spaces nor more than 8 characters.
That's for compatibility with DOS*, which couldn't handle spaces, or names longer than 8 characters.
*Early versions; later versions may have gained support?
The limitation was imposed by FAT, not by DOS.
True, but IIRC, DOS only supported FAT anyway.
-
On a related note, keeping "lists of shame" for software projects should be more common. I've been meaning to make and publish one for video games that fail to support alt tab, screen resolutions, and windowed mode properly.
-
@Gąska said in Big list of software that cannot handle spaces or accents in paths:
And another team at Microsoft created a short name "PROGRA~1", which has neither spaces nor more than 8 characters.
The short name generation is automatic, you make it sound like it was created specifically for Program Files.
@masonwheeler said in Big list of software that cannot handle spaces or accents in paths:
I recall hearing at one point that the reason Microsoft created the "Program Files" folder as the default location for installed programs was specifically to force developers to write software that could properly handle spaces in paths.
And then they gave up and renamed it "Programs" because it failed to get through the developers' thick skulls.No wait, I confused with "Documents and Settings".
-
@Zecc said in Big list of software that cannot handle spaces or accents in paths:
And yet, when it's installed by Visual Studio it is installed inside Program Files just fine. :person_of_undefined_gender_shrugging:
Well, Microsoft is good at creating workarounds for other people's bugs, so maybe they did that?
-
@Medinoc said in Big list of software that cannot handle spaces or accents in paths:
And then they gave up and renamed it "Programs" because it failed to get through the developers' thick skulls.
No they didn't:
-
@Kian said in Big list of software that cannot handle spaces or accents in paths:
@El_Heffe said in Big list of software that cannot handle spaces or accents in paths:
How is that even possible?
When your idea of inter-process communication is to use the command line to pass information between programs, the fact that command lines split tokens on whitespace presents problems that shitty programmers don't care to address. Yes, you can escape those, but then you wouldn't be a shitty programmer and wouldn't be using the command line in the first place.
The hard part is that *n*x expects escaped spaces in command lines, whereas Windows expects quoted arguments (with a way to escape quotes, further complicating the stuff).
-
All you accented name snowflakes should just suck it up and use unaccented lowercase version of your name for everything. It'd make it easier on everyone.
-
.
.
.
.
-
@cartman82 said in Big list of software that cannot handle spaces or accents in paths:
All you accented name snowflakes should just suck it up and use unaccented lowercase version of your name for everything. It'd make it easier on everyone.
On French Windows XP computers, the default name for the first user was "Propriétaire" (french for "Owner"). Or as DOS programs (and some non-DOS ones) saw it, "PropriÚtaire".