Hello, Untrusem <[email protected]> writes:
> So, I don't need to tell you that how bad forgejo search is. We don't > find the things that we are actually looking for. And this leads to: > > - Duplication of Work > - People asking the same things again and again because they can't find > it > - Me wasting 2 hours packaging things that are already there :( > > I have been using emacs-forgejo[1] that have eliminated my need of using the > browser for forgejo almost completely but it suffers with the same > issues as it uses forgejo's api. > > Through this email, I want to get a conversation going, how we can try > to solve this issue? and what other things people have tried that have > somewhat reduced it. > > [1] It is now unmaintained but works for me. I also find the default "fuzzy" search behavior of Forgejo often returns results of questionable quality. If you know the precise terms you're after I believe you'll get better results by 1. Double-quoting everything, to search for "literals" 2. prefix the literal pattern with "+", to make it "required"; So, if you want to find things related to openresolv for example, you could try +"openresolv", e.g. https://codeberg.org/guix/guix/issues?state=open&type=all&labels=&milestone=0&project=0&assignee=0&poster=0&sort=relevance&q=%2B%22openresolv%22 This is documented in https://forgejo.org/docs/latest/user/search/issue-search/ -- Thanks, Maxim
