Hey, just a heads up: capitalizing the first directory's name? Not cool. It feels like extra work when navigating paths, you know? Pressing shift along with a letter or number every time? Total drag, especially for everyday command line use.
> To that, I can only respond that, in a properly configured shell like the one that comes by default with GoboLinux, typing /Programs takes the exact same number of keystrokes as typing /usr: slash, lowercase p, Tab.
You know why it never bothers me when I navigate in PowerShell (or cmd.exe for that matter)?
Because the shell is helpful for me and don't try to force me to conserve precious ticks and memory of PDP-11 lacking any usability.
It's always amusing to hear 'case sensitivity rUl3z!' fans who totally miss what it's just the result of the constraints of the original systems. It's not a feature.
More so, it's explicitly addressed:
>> To that, I can only respond that, in a properly configured shell like the one that comes by default with GoboLinux, typing /Programs takes the exact same number of keystrokes as typing /usr: slash, lowercase p, Tab.
>> https://gobolinux.org/doc/articles/clueless.html
Just 'set completion-ignore-case On' and have your life immensively better. Why? Because you now would need one less Shift keystroke per every filename starting with capitalised letter even if you don't use GoboLinux.
Or continue like it's still 1977, why not, your VT100, your rules.
EDIT: oh, noticed this later:
> Why bother installing another shell instead of just sticking with bash for normal navigation?
Yes, you don't even bother to know your own shell.
Just saying... macOS does this by default, and a few months ago, I tried to delete a folder called `~/ladybird` and accidentally nuked `~/Library` instead. I wasn't expecting it to autocomplete a filename with a different case.
For non-Mac users, `~/Library` holds more or less all the state for your user account. With it gone, not only do you lose all settings and things, you can't even log in. I had a machine in a very unstable condition and no time to fix it.
I put it to sleep, left it for a month or so until I had a couple of hours spare, created a new user account with admin rights, copied all my files to that account, removed my damaged account, rebooted, created a new user account for myself, copied all my files back in, reset permissions as appropriate, and then logged in to it.
I then had to re-configure all my apps, which took most of the time. Now the machine was stable again, I cleared out the stuff in the admin account.
(No, it's not connected to my network TimeMachine, because it's my work laptop and I want to keep that stuff separate from my personal stuff on my home Macs. All the data is backed up to my company's cloud servers, but that doesn't store any macOS config stuff.)
So in the end, I just had to recreate my browser profiles, reimport my bookmarks and stuff, recreate all my email accounts in Thunderbird – because Mozilla still hasn't got Mozilla Sync for T'bird, dammit – and it was an inconvenience. No actual data lost.
But it has left me strongly conflicted on the subject of case-insensitive tab-completion.
Whether literally any shell can, I don't know. With zsh, bash and tcsh it is certainly possible.
set completion-ignore-case on