I'll be honest, I was coming to write to you all today to give windows another well-deserved roasting. Unfortunately, I found the same issue in Linux. Well, when I say issue, perhaps this is my own expecting something more logical from a system.
Lets take a look at the folder I'm talking about:
It's any folder you like, within it, I've created a folder called ".example", another without the leading period "example" and then a file which includes the word "example" within it's file name.
When I go to search this directory, with the explorer search bar within the window presented, I expect it to work by using exactly what I type...
So, if I search for "txt", only the "example.txt" file should come up, and it does...
But if I search for "example", I'm getting three results, as they contain the word, therefore I aim to be more specific and search for ".example"... The result of this last search:
Yup, I still get all three results. Clearly only one item matches ".example", and this annoys me.
And I jumped to Linux to take screen shots of this not working this way, but I found ls does work this way too... To be more specific I had to use "find":
This annoys me, I want the search to be specific, unless I add wildcards like "?" or "*" then I want what I type to be what it searches for, and if they have to put dumbed down searches in there, make it obvious that what you're getting is not an exact match.
The reason?... Imagine you have 300,000 files and you select 2,49 of then based on an exact filename search, and you give it a cursory glance, assume it to be correct, select all and delete?!?!?!
Yes, you end up deleting a load of stuff you didn't intend.
And I know, I know, I assumed what it was doing, and I know assumption is the mother of all fuck up, but still....
Even more annoying however, whilst setting up this example on windows, I did find something minor to moan about:
You can't create a folder which starts with a period in Explorer...
But you can with DOS/Command Prompt!
No comments:
Post a Comment