just off the top of my head, maybe the first thing is related to the fact that querying "foo" probably does literal/exact search, while "/foo" also matches prefixes?
(If you're confused by that, it's explained somewhere in the docs.)
You just separate filters with a space. So notebook:foo title:bar is OK.
A search with / is a basic search where foo is searched in all combinations (foobar, foo or tofoo) in the note content. A search title:foo search for a note with the word foo in the title, but not for foobar! A search title:/foo search for a /foo word in the title. In the searchfilters you can use Wildcards title:foo*
The search filters do not use wildcards by default and not all support wildcards! https://joplinapp.org/help/#searching
Thank you for the replies... I totally understand the difference between searching for foo and /foo, BUT what you have explained is not how it is working when using the data API.
I have a note with the title foo. When I use curl http://localhost:41184/notes I can see the note with the title foo.
Just to be clear... I am not trying to run these queries inside the terminal app! I am running the terminal app and the webclip server that is supposed to be supporting the data api.
My bad - didn't check the version. And also I am using the desktop app as I assume the code should be the same.
I noticed that if you search immediately after creating a note the search returns nothing, but once the search index has been updated the same query finds the note.
But this could be different between the CLI and desktop versions.