Earlier quoted context omitted.
I wonder if code to this effect has ever been written before for (int i = 1; i
Can that work for i > 9 ?
If you mkdir PROGRA~10, yes!
I'm “still afraid to use spaces in file names” years old
741–750 of 817 posts
Re: I'm “still afraid to use spaces in file names” years old
#742Re: I'm “still afraid to use spaces in file names” years old
#743Every week, I encounter a user - just like I did in the 80's - who cannot explain the difference between a file and a folder. "What do I use a folder for?", they ask, in the same breath that they request "some way to organize things logically". The no-filesystem movement has worked hard to eradicate this scourge from user experiences, but I fear that this is the devils work. Computer users should know what a file is…
> The no-filesystem movement Is that the movement to store all your data as an amorphous pile of crap, and then provide easy-to-use search tools to actually find the content you're looking for? On one hand, I really like the search tools that come from this. But I still like to actually organize my data, so I can browse it if I want to. Also, these search tools seem to only work well enough on macOS and fall flat on…
You had me at "amorphous pile of crap", but lost me at 'actually find the content'... ;)
Meanwhile, I've got a single directory full of PDF files (over 60,000+) which I routinely "ls -alF | grep " for, and I've also got some PyPDF scripts for doing deeper content search - but yet I yearn for a way to automatically parse the filenames and organize things categorically into a folder tree resembling a word cloud, symbolic links and all .. one of these days ..
Re: I'm “still afraid to use spaces in file names” years old
#744In the shell spaces have to be escaped which is annoying. This doesn't change with age I think
Re: I'm “still afraid to use spaces in file names” years old
#745I work on a complex desktop application, and it's been astounding the number of bugs that have appeared over the years triggered by spaces and other unusual characters in file names. If you do anything with subprocesses or path processing, it's absurdly easy to hit in a thousand different ways, over and over again. Pro tip: rename your development directory (or even better: the workspace path in CI) to put a space an…
I did something similar on accident. I used to keep all my development work synced with Dropbox and I had a work and a personal account. So any of my own projects would have /Dropbox (Personal)/ in the path which did catch some bugs. Dropbox renamed my folder to "Dropbox (Personal)" automatically when connecting a work account.
Re: I'm “still afraid to use spaces in file names” years old
#746Earlier quoted context omitted.
I've had issues when moving between Window/*nix file systems, where Windows file names are case insensitive and *nix systems are case sensitive. Build script works fine locally on Windows, but then chokes in *nix test server, as it's effectively a different path.
file names aren't case insensitive, it's the windows API that is
I assume you mean that the Windows API (standard for Windows apps) is case insensitive, but if using the WSL (Windows Subsystem for Linux) it's possible to get case sensitivity: https://docs.microsoft.com/en-us/windows/wsl/case-sensitivit...
Re: I'm “still afraid to use spaces in file names” years old
#747Earlier quoted context omitted.
Overly aggresive is right! I don't know if this is genius or deranged! I'm leaning towards genius and stealing the idea. By the way: what's your beef with en dashes? I mean, if it was "everything should be 'HYPHEN-MINUS' (U+002D)", then fine, but why specifically en dashes and not em dashes?
I totally agree that for some people, this could be a terrible command to have around. However, I know that it has been working for me for about 8+ years or so. I almost always run in in my ~/Downloads folder on files that I don't really care about. I download a lot of academic papers and books, and this just saves me a lot of time to put files in the format I like: author--paper-title.pdf. And that's part of the rea…
For a download folder in particular, this does sound like a great idea. You'd break the list in the browser or whatever, but who cares about that?
Re: I'm “still afraid to use spaces in file names” years old
#748Software engineers - particularly of the more embedded variety - absolutely still have this problem.
The main culprit is GNU Make which does not cope with spaces in filenames. As far as it is concerned an array is a string separated by spaces so it gets very confused. Yes there are some partial workarounds, no none of them consistently work. You learn very quickly to check all code out in a file tree with no spaces in it, otherwise builds can randomly break in strange ways. It's not always clear up front whether Make is going to be involved somewhere in the build, so it's just easier to be safe.
Re: I'm “still afraid to use spaces in file names” years old
#749Earlier quoted context omitted.
Cries in nixpkgs (Anyone who tried to package a program that hardcodes the “usual” binary paths know the pain)
Doesn't nix itself hardcode the nix store path though?
Afaik there is an option to change it, but it is not advisable as that will break the binary cache and you are left with compiling everything yourself. This is due to a technical limitation in that different packages can contain paths everywhere and thus they are inherently part of the resulting hash, on which other packages can depend.
Re: I'm “still afraid to use spaces in file names” years old
#750Earlier quoted context omitted.
I mean we're heading there with /usr being your /System. Redhat/Pottering are doing heroic work in this space. /Users -> /home /System -> /usr /Data -> /var /Config -> /etc /Boot -> /boot /Ephemeral Temp -> /run /Persistent Temp -> /tmp The only real holdouts are proc/sys/dev which are the kernel and mnt/media/opt/srv which are really for the user/sysadmin and aren't really used by the OS anymore.
I'm not sure I'm a fan of the capitalization and spaces, other than that I'm all for more self-explanatory names.
Why not? That's how proper English text is written. Of course there are many programs that can't handle it properly (or handles it inconveniently) so in practice it might be problematic at times, but otherwise I see nothing wrong with it.