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

using multiple search terms returns a union of matches, rather than an intersection #3

Closed
AndydeCleyre opened this issue Feb 3, 2017 · 1 comment
Assignees
Milestone

Comments

@AndydeCleyre
Copy link

yay 1.95

Here are some searches that act surprisingly differently from yaourt:

Args Yaourt Results Yay Results
yay compiled 1 2
firefox kde 2 304
simple kde 21 1816
@Jguer Jguer self-assigned this Feb 3, 2017
@Jguer
Copy link
Owner

Jguer commented Feb 3, 2017

In reality it doesn't even return an OR of the matches, it returns a number menu on each term. :shame:

  • yay <term1> <term2>has almost no practical utility right now versus writing yay <term1> and then yay <term2>
  • Narrowing the search further is useful.
  • It's simple enough to implement with almost no performance cost.

Will implement
Using strings.contains on each <>:
<term1.name> AND (<term2>.description OR <term2>.keywords) AND (<term3>.description OR <term3>.keywords) AND ... will probably return the best search results.

<term1.name OR term1.description> AND (<term2>.description OR <term2>.keywords) AND (<term3>.description OR <term3>.keywords) AND ... will probably return a broader result (hopefully not by much). To test.

@Jguer Jguer added this to the 1.100 milestone Feb 4, 2017
@Jguer Jguer closed this as completed in 1f4bb8e Feb 18, 2017
Morganamilo pushed a commit that referenced this issue Nov 13, 2019
Pass applicable config options to alpm and provide a method for ignorepkg checking
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants