Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

search unreliable, doesn't seem to find partial matches #6455

Closed
aleqx opened this issue Apr 25, 2022 · 7 comments
Closed

search unreliable, doesn't seem to find partial matches #6455

aleqx opened this issue Apr 25, 2022 · 7 comments
Labels
stale An issue that hasn't been active for a while...

Comments

@aleqx
Copy link

aleqx commented Apr 25, 2022

I'm trying to migrate from Evernote to Joplin. I have a note titled "Capacitors for Samsung monitors". Inside that note the body text also has lots of occurrences of the word "capacitor". If I type "cap" in the search box, it doesn't find this note at all. If i type "capacitors" it does find it. I'm hoping this is a bug ... or else the find feature isn't that useful for me (I have thousands of notes that I'd like to partially match search on).

In fact, searching for "cap" finds only 2 notes, both where the string "cap" is matched inside the body text, one with a full match on the word M5G.CAP and the other on partial matches on the word badcaps.

Evernote finds 43 notes, with the string "cap" partially matched in both titles and body, on every string, as I expected (e.g. "capping" etc).

Evernote and Joplin have the same notes (imported from enex).

Joplin 2.7.15 (prod, win32)
Client ID:
Sync Version: 3
Profile Version: 41
Keychain Supported: Yes
Revision: 8352e23

@aleqx aleqx added the bug It's a bug label Apr 25, 2022
@Daeraxa
Copy link
Collaborator

Daeraxa commented Apr 25, 2022

https://joplinapp.org/help/#searching

By default it uses full text searching, if you need basic search then you need to add wildcards or swap to basic mode i.e. cap* or /cap

Curious that it managed to find badcaps though

From the above link

For example, searching for cat will return all the notes that contain this exact word. Note: it will not return the notes that contain the substring - thus, for "cat", notes that contain "cataclysmic" or "prevaricate" will not be returned.

One drawback of Full Text Search is that it ignores most non-alphabetical characters. However in some cases you might want to search for this too. To do that, you can use basic search. You switch to this mode by prefixing your search with a slash /. This won't provide the benefits of FTS but it will allow searching exactly for what you need. Note that it can also be much slower, even extremely slow, depending on your query. | /"- [ ]" - will return all the notes that contain unchecked checkboxes.

You can also use goto anything for a quick search (ctrl + p) which will match "cap" to "capacitors"

@Daeraxa Daeraxa removed the bug It's a bug label Apr 25, 2022
@aleqx
Copy link
Author

aleqx commented Apr 25, 2022

I see. Thanks for pointing that out. I wasn't expecting in this day and age for real-time search to not match partially, hence why I didn't read docs to find out if I'm doing something wrong.

It's curious that ctrl+p search and the general search box use different search syntax. In fact, I wonder why use two search features in the first place.

p.s. Perhaps "badcaps" is matched because you bound on known words like "bad" even when word boundaries don't exist?

@Daeraxa
Copy link
Collaborator

Daeraxa commented Apr 25, 2022

Goto anything is meant to be a quick way of jumping between notes, notebooks, tags etc. whereas the "full" search is designed for far more complex queries and filters to be made.

The reason for the full text search is mostly speed related (although personally I've never noticed the "basic" search to be particularly slow).

@ferrlen
Copy link

ferrlen commented May 24, 2022

I must say I agree with aleqx, it's confusing for newcomers to have full matches in the search box, I think most new users would expect it to search for partial matches. I also thought the search was broken at first. I think it'd be a good idea to have the goto search bar by default instead of the current search bar, and let the user change this in a menu if they want to

@github-actions
Copy link
Contributor

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

@github-actions github-actions bot added the stale An issue that hasn't been active for a while... label Jun 24, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Jul 2, 2022

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.

@koppor
Copy link

koppor commented Nov 15, 2023

@ferrlen Alternatively, one can use Ctrl+P to get a nice realtime fulltext search.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale An issue that hasn't been active for a while...
Projects
None yet
Development

No branches or pull requests

4 participants