I did, because they’re different ways of expressing the same meaning. They all mean (apologies for borrowing mathematical notation for linguistic applications) |file|. I don’t care what the expression of a thing is, I care about meaning. And as a result, when I save a file and then search to recall it, it should not matter what case it’s in - only for the meaning to match. The state of my shift or capslock should be totally immaterial.
Then why should it allow me to save different expressions of the same meaning ever? If it’s going to let me search for it case-insensitive, just head the matter off at the pass and save it that way. Either that, or automatically create link files for every case permutation to the same folder as soon as the file exists.
I did, because they’re different ways of expressing the same meaning. They all mean (apologies for borrowing mathematical notation for linguistic applications) |file|. I don’t care what the expression of a thing is, I care about meaning. And as a result, when I save a file and then search to recall it, it should not matter what case it’s in - only for the meaning to match. The state of my shift or capslock should be totally immaterial.
Whatever you use to search can just be case insensitive, which is how most file browsers work on Linux.
Then why should it allow me to save different expressions of the same meaning ever? If it’s going to let me search for it case-insensitive, just head the matter off at the pass and save it that way. Either that, or automatically create link files for every case permutation to the same folder as soon as the file exists.