3 ms·

Side note - after all these years I still don't feel comfortable with using special characters (like ą, ż, ź) and spaces in filenames in Windows. DOS times sit

Side note - after all these years I still don't feel comfortable with using special characters (like ą, ż, ź) and spaces in filenames in Windows. DOS times sit deeply in my soul and It just doesn't feel right.

klyrs 5y ago
I've learned to live without file extensions... but I still wince at 4-letter file extensions. I haven't used windows in almost 20 years.
- Tagbert 5y ago
  Do your files really not have file extensions or is it just that they are hidden by default in the file browser? In Mac OS extensions are important but they are hidden by default. I always force them to be shown when I setup a new Mac. Hiding them obscures important information. Hiding them offers nearly no benefit.
  - klyrs 5y ago
    I use Linux exclusively, where file extensions are entirely optional. While, yes, they are shown in the file browser, that's a tool of last resort for me: my display is typically a grid of terminals and I do most of my work through them. Text files, such as executable scripts with shebangs, do not get file extensions. Plain text files, such as when I'm taking notes about something, do not get file extensions. Stuff like images, music, etc get file extensions.
renewiltord 5y ago
This is amusing but my filesystem has no spaces in it. It's still a pain in the ass from the command line to handle spaces and instead of `-print0` and all that shit I just ban spaces from my filesystem. `-` and `_` are sufficient as spacers. I know zsh handles auto-complete well but I can `y-a-w` out of my `nvim` `:terminal` a lot easier.
- enriquto 5y ago
  I like this approach. How do you enforce your ban? Is there a mount(8) option for that? Or do you simply avoid these filenames "by hand"? What happens if you untar an archive and it contains filenames with spaces?
  - renewiltord 5y ago
    Haha, I do not enforce the ban. You are correct. If I untar'd something I'd be sitting there with a space there and I'd look like a fool. In practice, most of these files are in my `~/Downloads` and I don't really keep them around there very much.
KSPAtlas 5y ago
It hurts readability because l and ł are completely different
voussoir 5y ago
Windows user here. I feel that the computer should work for the human, not the other way around. I use whatever unicode characters are appropriate for the file, except the minimum set of disallowed characters: colon, slash, asterisk... Any tool that can't handle that is faulty, and I'll either stop using it or make a temporary symlink to get the job done. But most tools are fine with unicode these days. Of course I speak from the perspective of a personal computer situation with no deadlines or business requirements or software limitations. I still use the old cmd.exe with the Terminal font. It doesn't even render most unicode properly, they come out as ?. I deal with it because I like cmd.exe and I like Terminal and I'd rather see ? than butcher the file's name by romanizing it.

klyrs 5y ago

I've learned to live without file extensions... but I still wince at 4-letter file extensions. I haven't used windows in almost 20 years.

Tagbert 5y ago
Do your files really not have file extensions or is it just that they are hidden by default in the file browser? In Mac OS extensions are important but they are hidden by default. I always force them to be shown when I setup a new Mac. Hiding them obscures important information. Hiding them offers nearly no benefit.
- klyrs 5y ago
  I use Linux exclusively, where file extensions are entirely optional. While, yes, they are shown in the file browser, that's a tool of last resort for me: my display is typically a grid of terminals and I do most of my work through them. Text files, such as executable scripts with shebangs, do not get file extensions. Plain text files, such as when I'm taking notes about something, do not get file extensions. Stuff like images, music, etc get file extensions.

renewiltord 5y ago

This is amusing but my filesystem has no spaces in it. It's still a pain in the ass from the command line to handle spaces and instead of `-print0` and all that shit I just ban spaces from my filesystem. `-` and `_` are sufficient as spacers. I know zsh handles auto-complete well but I can `y-a-w` out of my `nvim` `:terminal` a lot easier.

enriquto 5y ago
I like this approach. How do you enforce your ban? Is there a mount(8) option for that? Or do you simply avoid these filenames "by hand"? What happens if you untar an archive and it contains filenames with spaces?
- renewiltord 5y ago
  Haha, I do not enforce the ban. You are correct. If I untar'd something I'd be sitting there with a space there and I'd look like a fool. In practice, most of these files are in my `~/Downloads` and I don't really keep them around there very much.

KSPAtlas 5y ago

It hurts readability because l and ł are completely different

voussoir 5y ago

Windows user here. I feel that the computer should work for the human, not the other way around. I use whatever unicode characters are appropriate for the file, except the minimum set of disallowed characters: colon, slash, asterisk... Any tool that can't handle that is faulty, and I'll either stop using it or make a temporary symlink to get the job done. But most tools are fine with unicode these days. Of course I speak from the perspective of a personal computer situation with no deadlines or business requirements or software limitations. I still use the old cmd.exe with the Terminal font. It doesn't even render most unicode properly, they come out as ?. I deal with it because I like cmd.exe and I like Terminal and I'd rather see ? than butcher the file's name by romanizing it.