4 ms·

I had a guy in my team use forward slashes in filenames. Terrible idea, caused all sorts of weird issues.

• mrweasel 5y ago
  But nice for testing. I spend a few month on Windows while doing a Django project and found a number of bugs no one else discovered because they used Mac or Linux.
• zokier 5y ago
  Did you mean backslashes? I don't know if any filesystem/OS supports forward slashes in filenames
  • kps 5y ago
    OS X does in the GUI; they're isomorphic to ‘:’ at the UNIX level. (The Mac used ‘:’ as the directory separator.)
    • rootbear 5y ago
      And a : in a file name at the GUI level gets turned into a dash! I just tried to name a text file "Foo/Bar 10:01.rtf" and it changed it to "Foo/Bar 10-01.rtf"!
      • kps 5y ago
        In that case the GUI is merely changing the file name you type; in a shell you'll see it as "Foo:Bar 10-01.rtf".
• danachow 5y ago
  How was this possible? None of the mainstream operating systems allow this.
  • distant_hat 5y ago
    via GUI in OS X.
    • danachow 5y ago
      Ah so that’s not really putting a slash in the name on disk - finder is just displaying the colon that way - it substitutes with a colon for historical reasons that have to do with pre OSX MacOS (but you can see if you create a file from a program or the command line with a colon in it, it will display as a slash in finder). It shouldn’t cause any problems on its own on the system - but the colon is troublesome if you have to interact with DOS/Windows lineage machines.