2 ms·

This is a personal reason, but the reason I prefer case sensitive directory names is I can make "logical groupings" for things. So, my python git directory migh

This is a personal reason, but the reason I prefer case sensitive directory names is I can make "logical groupings" for things. So, my python git directory might have "Projects/" and "Packages/," and the capitalization not only makes them stand out as a sort of "root path" for whatever's underneath, but the capitalization makes me conscious of the commands I'm typing with that path. I can't just autopilot a path name, I have to consciously hit shift when tab completion stops working. That might sound like a dumb reason, but it's kept me from moving things into the wrong directory, or accidentally removing a directory multiple times in the past. I also use Windows regularly and it really isn't a hindrance, so maybe I wouldn't actually be bothered if everything was case sensitive.

pwagland 2y ago
TBF, you don't need case sensitive FS for that, just case retaining is enough. And then have the option on how to sort it.
- josephcsible 2y ago
  Don't you need case sensitivity for this part? > I can't just autopilot a path name, I have to consciously hit shift when tab completion stops working. On a system that's case retaining but not case sensitive, wouldn't "pr" autocomplete to "Projects"?
  - zoky 2y ago
    No, MacOS doesn’t do that. `cat Foo` and `cat foo` will both work, but only the first one will tab complete if the file is called `Foo`.
    - chuckadams 2y ago
      zsh tab-completed both just fine, preserving the case in both. I’d have preferred it corrected the case, but meh.
notjoemama 2y ago
I like it! That's a great idea. To me, this sounds like a great practice for terminal environments but may be less intuitive when using file system apps. I could easily overlook a single letter capitalization in a GUI view of many directories. Maybe it's because at a terminal the "view" into the file system is narrow? Now I'm wondering how I can use this in my docker images. I mean that might irritate devops. Well, maybe they'll like it too. Man, thanks for posting this.

pwagland 2y ago

TBF, you don't need case sensitive FS for that, just case retaining is enough. And then have the option on how to sort it.

josephcsible 2y ago
Don't you need case sensitivity for this part? > I can't just autopilot a path name, I have to consciously hit shift when tab completion stops working. On a system that's case retaining but not case sensitive, wouldn't "pr" autocomplete to "Projects"?
- zoky 2y ago
  No, MacOS doesn’t do that. `cat Foo` and `cat foo` will both work, but only the first one will tab complete if the file is called `Foo`.
  - chuckadams 2y ago
    zsh tab-completed both just fine, preserving the case in both. I’d have preferred it corrected the case, but meh.

notjoemama 2y ago

I like it! That's a great idea. To me, this sounds like a great practice for terminal environments but may be less intuitive when using file system apps. I could easily overlook a single letter capitalization in a GUI view of many directories. Maybe it's because at a terminal the "view" into the file system is narrow? Now I'm wondering how I can use this in my docker images. I mean that might irritate devops. Well, maybe they'll like it too. Man, thanks for posting this.