I don't think most people use oh-my-zsh. It's very popular, and a lot of people use it, but I think most is a stretch.
Either way, it's just a set of plugins and configs so of course you can get it to work on any setup. Just saying that it's not inherent to zsh, and you can probably get similar behavior in most shells with a similar config.
I remember having that when I used OhMyZsh, but after going back to a more bespoke config it doesn't work anymore. Also tried using zsh as a different user to ignore my own configs, that doesn't work either.
tldr, it's not default zsh behavior.
Reasonable and sane behavior of cd. Just get into the habit of always using lower case names for files and directories, that's how our forefathers did it.
That's a promising idea, apparently my $TERM is not foot but xterm-256color by default. However starting with TERM=foot br or TERM=foot broot doesn't seem to enable high res previews. :(
Anyone know if I can get the highres image previews in foot? I think I saw something about foot supporting the kitty graphics protocol, but I can't get it to work. If I start it like normal I get low res previews, if I start it with TERM=kitty I get no previews.
I think we'd all be quite shocked if Steve Jobs did that. But Apple might.
Prompt better. I use it extensively and the code I get is usually a good start. But it can't do anything.
If a directory has multiple words in it I usually do kebab case: i-like-mine-in-a-way-i-can-read-them-properly. Both easier to read and type than pascal case.
For more complex filenames I use a combination of kebab-case and snake_case, where the underscore separates portions of the file name and kebab-case the parts of those portions. E.g.
movie-title_release-date-or-year_technical-specifications.mp4