3 ms·
Try setting the insensitive option in your shell. With hidden filenames on mobile, desktop GUIs, terminal CLI completion, and shells with insensitive matching
by mixmastamyk 6y ago
Try setting the insensitive option in your shell.
With hidden filenames on mobile, desktop GUIs, terminal CLI completion, and shells with insensitive matching like fish (bash via option), the benefits of insensitive fs are not as high as they used to be.
Meanwhile, the complexity of matching modern Unicode causes performance degradation and exposes many edge cases.
In short, the window of time where insensitive made sense has largely closed.
- lmm 6y ago> With hidden filenames on mobile, desktop GUIs, terminal CLI completion, and shells with insensitive matching like fish (bash via option), the benefits of insensitive fs are not as high as they used to be. We've got better at working around case sensitivity, sure. I don't see that as a good reason not to fix the problem properly.
- mixmastamyk 6y ago> Meanwhile, the complexity of matching modern Unicode causes performance degradation and exposes many edge cases. As mentioned, there is no way to "fix the problem properly" and a close-enough solution, rarely needed these days, slows performance.