4 ms·
Try doing that in e.g. Make
by mehrdadn 6y ago
Try doing that in e.g. Make
- fao_ 6y agoTry finding out which registry key you need to edit to get something to happen. Some things across different systems have pitfalls as a result of their implementation, or some features have pitfalls. There are half a dozen things I can point to on windows that are worse than the "spaces in filenames". Hell, windows doesn't even support ISO 8601 dates, or times to be properly placed in files. It restricts symbols much more than Linux / Unix
- yzmtf2008 6y agowho said anything about windows?
- fao_ 6y agoThe parent thread referenced windows as something that handles spaces in filenames. I'm not sure why I'm getting downvoted when my comment was relevant to the debate occurring, and my point (that all features have downfalls caused by the necessity of implementation within the surrounding system, and in the case of command line arguments, linguistics and common keyboards themselves) is something that according to the guidelines should be debated against, not downvoted.
- yzmtf2008 6y agoNone of the parents of your comment mentioned Windows. Perhaps you have the wrong thread?
- blacksqr 6y agoIn the early 2k's I discovered that it was impossible to quote or escape spaces in filepaths in a makefile. I naively reported it to the Make maintainer as a bug. The maintainer responded by saying, basically, that the behavior was deeply baked in and was not going to change.
- enriquto 6y agoThis is a nice feature of make. People who put spaces on filenames are justly punished by not being given the goodness of make.