There doesn't seem to be way to find phrases?

[Biomarx]

If i search for a rem cmd-P and type in a phrase i know i used e.g. “in time” i get all the rems with “in” and “time” - even using ` or ’ or " to bracket the phrase doesn’t do the trick.

I feel like this is a bug because if want to search for a name on a long page (Jim Smith), with cmd-F, the default is all the Jim’s and all the Smith’s. If i search for title like “The Way”, i get all the the’s etc.

only with backtick Jim Smith do i get the result i want, and only finding in a page. Not with rem-search cmd-P.

maybe i’m missing something? (Using mac app 1.5.0, and browser on mac)

[UMNiK]

You aren’t missing anything, see

Ability to use logical operators for searching (Queries)

For all sorts of search, Ctrl + F, Ctrl + O and especially for search portals, adding the ability to use logical operators like and, or, not to combine search terms (like text, tags, references) will make search feature really powerful. E.g. create a search portal with rems that are tagged with both task and high priority. Also, it would be cool if we can use something like parentheses () to control the precedence of these operators just like in typical logical expressions. E.g. task and (high…

[Danny]

Hi @Biomarx! As @UMNiK indicated, you aren’t missing anything (I’m the remnote dev primarily working on search at the moment). Rem are currently searched on each individual word (or character sequence) in the query. As was mentioned in some of our recent changelogs, I’m currently devoting most of my attention to building out “instantaneous” search that should provide a more frictionless search experience for users with any size knowledge base. That said, the team is aware of the different requests that have been floating around the community for a more powerful querying experience, so that will definitely be on our minds as we determine how to move forward with search in the future!

[Biomarx]

Thanks @UMNiK and @Danny , Yes, it is really the absence of phrase searching that really trips me up. I’ve loaded a few hundred sets of highlights from papers (exported annotations from PDFexpert), so really need some better ways to locate rems.

[Biomarx]

reverse problem i am now struggling with: i would like a search portal for PAR (since i’ve been taking notes on “practice as research” and that is the abbreviation).

Is there any way to find just the rems with PAR and not everything with “part” and “parable” and “reparations”? I get 100 hits and almost none of them are the ones i want (100 seems the limit, so i literally don’t get the ones i want since so many have “part” in them). It is as if the word always has wildcard * after it. Is there a way to insert a word-end?

what am i missing? Is there any way to search for a short word? If not, i realize I truly can’t use this until it is fixed. @UMNiK and @Danny

i really don’t want to have to port it all to workflowy (where i can search for par and it show them all until i hit spacebar and then just the PAR ones are left - this seems critical)

thanks, joe

[UMNiK]

Alas, that would also fall under queries that are yet to be implemented. However, there is already some prioritisation within search, in your case manually selecting “PAR” a few times will place it higher in the results over time.
Read more here

Settings: Search parameters/weights

The search powering Ctrl + P, Ctrl + S, [[ and so on uses some smart filtering and weighting to always show the most relevant rem. E.g. Matching prefixes are weighted higher than text at the end Text in a rem is weighted higher than text in a parent (probably) Text in references is ignored The accepted search result is recorded, so if you always select Custom CSS when typing css it will rank higher over time, even if you have a CSS Tricks rem. There is probably more smartness. Since a few we…

[Danny]

Yes, this is a known issue. After we get the new search out, we’re looking into ways to make search prioritization better/more transparent/more customizable. Right now there are a variety of workflows where search doesn’t seem to return the “right” results, even though it isn’t exactly a bug. Thanks for bringing this up though @Biomarx, it helps me to know specific use-cases to be building around!