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 function is unhelpful #6349

Closed
0scvr opened this issue Mar 30, 2022 · 9 comments
Closed

Search function is unhelpful #6349

0scvr opened this issue Mar 30, 2022 · 9 comments

Comments

@0scvr
Copy link

0scvr commented Mar 30, 2022

Environment

Joplin version: Joplin 2.7.15
Platform: macOS
OS specifics: version 12.3

Describe what you expected to happen

Should be able to find notes without typing the whole word.

I've seen other people complain about the search function. Perhaps it should be improved (fuzzy search ?).

Capture 2022-03-30 à 17 17 21
Capture 2022-03-30 à 17 17 27
Capture 2022-03-30 à 17 17 31

@0scvr 0scvr added the bug It's a bug label Mar 30, 2022
@hihihlo
Copy link

hihihlo commented Mar 31, 2022

you should use "mous*" rather than "mous".
Joplin readme.md said :

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.

@kacnje
Copy link

kacnje commented Mar 31, 2022

I also noticed that many of my colleagues have problems when searching. Almost all of them (and I stand with them :-)) said that this should be a setting and default should probably search for notes containing the substring.
Next to this, Joplin should HIGHLIGHT results in notes. Currently, it is really annoying when notes are longes and you have to repeat searching in it.
I can't say for Mac, but searching behavior is annoying on Windows and Linux (I use the Android version only occasionally and can't speak about it). My experience is that this bothers many users.
Otherwise, the Joplin is a really nice application.

@hihihlo
Copy link

hihihlo commented Mar 31, 2022

very much agree !

  1. suggest Joplin auto search [*cat* *dog*] when input [cat dog], or provide a option setting (e.g. "auto contain substring").
    this is Intuitive and frequently use.
    in ANY text editor, everyone expect [cat] will match [catalog]
    (unless use regex like [\bcat\b], or checked "whole word")
  2. in above setting, if need word boundaries e.g. [cat*] or [*dog], maybe can add search filter "bound:",
    e.g. [bound: cat* dog] matched "catalog about dog", and not match "catalog about doggy"
    thanks~

@0scvr
Copy link
Author

0scvr commented Mar 31, 2022

you should use "mous*" rather than "mous". Joplin readme.md said :

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.

My mistake, I wasn't aware this was the expected behaviour. However, as @kacnje said, I think it would be better if the default behaviour was to search for substrings. I think this is more intuitive and more useful for most.

@0scvr
Copy link
Author

0scvr commented Mar 31, 2022

very much agree !

  1. suggest Joplin auto search [cat dog] when input [cat dog], or provide a option setting (e.g. "auto contain substring").
    this is Intuitive and frequently use.
    in ANY text editor, everyone expect [cat] will match [catalog]
    (unless use regex like [\bcat\b], or checked "whole word")
  2. in above setting, if need word boundaries e.g. [cat*] or [dog], maybe can add search filter "bound:",
    e.g. [bound: cat
    dog] matched "catalog about dog", and not match "catalog about doggy"
    thanks~

Yes, something like that or a regex mode would would make more sense in my opinion.

@pth0rn
Copy link

pth0rn commented Mar 31, 2022

Using * in search only works after the word, and not as a prefix.
E.g. "*bar" does not return any results if a note has "foobar"
Feel like proper search is very important, I hope it gets implemented

@Daeraxa
Copy link
Collaborator

Daeraxa commented Mar 31, 2022

Closing issue as it is not a bug, instructions on how to use the search function is covered in the documentation - https://joplinapp.org/help/#searching. If there is any feedback on the documentation then feel free to discuss on the forums or create a PR.

By default Joplin uses full word searching for speed but you can switch to basic search mode by adding a / before your search.
i.e./bar would find notes that contain bar and foobar

@Daeraxa Daeraxa removed the bug It's a bug label Mar 31, 2022
@Daeraxa Daeraxa closed this as completed Mar 31, 2022
@koppor
Copy link

koppor commented Nov 15, 2023

Is there a possibility to configure Joplin to always have partial-string search. I have a machine being powerful enough to do search-as-you-type? Reason: I am currently evaluating alternatives to Microsoft OneNote - and I don't want to type more characters for a "similar" search behavior.

@koppor
Copy link

koppor commented Nov 15, 2023

Reading https://joplinapp.org/help/apps/search#goto-anything, I learned that one should not use the search box, but should use Ctrl+P to activate a nice fulltext search.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants