I have many thousands of files which have keywords inside []. I also use {} and () for other purposes, so I can't just change.
I used to be able to search using [keyword], but it doesn't work any more and I can't find anything in the settings to allow or exclude certain chars. I'm also not using Regular Expressions, so there's no reason [] should be excluded.
Using '[' alone returns no results.
Using ']' alone returns the entire database.
This is a recent change.
1.9.8 64bit (Dec 4 2025) - LibFormat 7.230 (MacOS)
"[" & "]" no longer work as chars in search on filename
Re: "[" & "]" no longer work as chars in search on filename
There are multiple ways to search on the filename, and you do not specify what exactly you are doing.
I can confirm searches for [ and ] do not work as expected when using the "Filename" field at the top of the search dialog.
However, if you add Filename as a condition (or Filename with extension, or File path) then then searches for those characters do work properly.
Use that method until Pierre can attend to this.
In the future, where you're doing things that have multiple approaches, it's best to either be very specific or provide a screenshot to document specifics.
Also, FYI, searching against filename as a condition is more flexible, as you can use booleans and multiple conditions, and you can also save repetitive searches of this type as Smart Albums.
I can confirm searches for [ and ] do not work as expected when using the "Filename" field at the top of the search dialog.
However, if you add Filename as a condition (or Filename with extension, or File path) then then searches for those characters do work properly.
Use that method until Pierre can attend to this.
In the future, where you're doing things that have multiple approaches, it's best to either be very specific or provide a screenshot to document specifics.
Also, FYI, searching against filename as a condition is more flexible, as you can use booleans and multiple conditions, and you can also save repetitive searches of this type as Smart Albums.
Re: "[" & "]" no longer work as chars in search on filename
In the future, don't be such a condescending prig.In the future, where you're doing things that have multiple approaches, it's best to either be very specific or provide a screenshot to document specifics.
Also, FYI, searching against filename as a condition is more flexible, as you can use booleans and multiple conditions, and you can also save repetitive searches of this type as Smart Albums.
While your suggestion to use the Filename condition is in fact a good one. I've never even noticed that before since it's been unnecessary. The rest of your post smacks of a smugness which isn't appreciated or needed. I'm willing to bet that I have far more experience, (which includes >45 years as a developer) working with computers and software than you do. That my post wasn't to your liking is understood. You've made that abundantly clear.
Perhaps next time if you need clarification, you'll ask for it instead of pontificating.
Thank you for the suggested work-around.
Re: "[" & "]" no longer work as chars in search on filename
In the future, you know where you can go you self aggrandizing arrogant little pos.
You are in fact wrong, both about our relative experience and about my intentions. I had no objections to the tone or content of your post, other than you could have provided more specific information about what you were specifically doing. Which is a fact. I was giving you facts. And instead of making you jump through hoops and restate your issue or provide screenshots, I spent my own time to work out what you were actually doing, and tested all the various options, to both confirm your assertion of a bug and give you accurate information about a workaround.
But you have such a chip on your shoulder and such a falsely inflated opinion of your own abilities that you jump to the conclusion that someone who speaks plainly and gives you facts that you didn’t know must be condescending to you, when obviously you must be deferred to and revered. Grow up and act like an adult, it’s well past time.
Your claims of experience ring pretty hollow when you can’t manage to write a more specific account when reporting a bug, and can't be bothered to explore the features of the search enough to be aware of the other ways to search filename. Oh, there was no need. I didn’t take issue with that originally; it was just a standard user situation. But in light of your protestations about your vast experiences, now it really just seems amateurish.
So don’t worry, there won’t be any next time. I will be ignoring your account and you will receive no more help from me. I will not waste any more time on someone of your character.
You are in fact wrong, both about our relative experience and about my intentions. I had no objections to the tone or content of your post, other than you could have provided more specific information about what you were specifically doing. Which is a fact. I was giving you facts. And instead of making you jump through hoops and restate your issue or provide screenshots, I spent my own time to work out what you were actually doing, and tested all the various options, to both confirm your assertion of a bug and give you accurate information about a workaround.
But you have such a chip on your shoulder and such a falsely inflated opinion of your own abilities that you jump to the conclusion that someone who speaks plainly and gives you facts that you didn’t know must be condescending to you, when obviously you must be deferred to and revered. Grow up and act like an adult, it’s well past time.
Your claims of experience ring pretty hollow when you can’t manage to write a more specific account when reporting a bug, and can't be bothered to explore the features of the search enough to be aware of the other ways to search filename. Oh, there was no need. I didn’t take issue with that originally; it was just a standard user situation. But in light of your protestations about your vast experiences, now it really just seems amateurish.
So don’t worry, there won’t be any next time. I will be ignoring your account and you will receive no more help from me. I will not waste any more time on someone of your character.
Re: "[" & "]" no longer work as chars in search on filename
I looked through a bit of your post/comment history, and you are condescending to many people. I understand that you'll never realize that, but a little self-assessment may be warranted. On that note, I bid you adieu. Please, keep your word.