How to Properly Search the QubesOS Repository on Github

When you use any tool, whether Qubes or a search engine, you must
learn how it works, and think.

Take this case. That search gives you 2 results.

  1. The first refers to “documentation” with a link that looks good, but
    gives a 404 error.
    What now? Why not look at the repo that used to contain the page.-
    https://github.com/QubesOS/qubes-core-qrexec
    There isn’t a “documentation” directory at all. So it isn’t just that
    page that’s gone, but the whole directory. Where has it gone? Maybe it’s
    in the README, or perhaps that directory has been renamed. What might be
    other terms for “documentation”? docs? doc? readmes? notes? man?
    Well look, there’s a “doc” directory, and in there is the file you are
    looking for.
  2. The second result starts with another link - again a 404. A quick
    skim down the page to the last comment gives you a link to the relocated
    page.

As Aretha taught us, Think.

A basic thing to learn in life is that what works in one place wont
necessarily work in another.
Don’t enter a poker competition if you are a chess GM.
Don’t use GitHub syntax on google.

Think.

It’s asking you to sign in. Why?
I remember you - you’re the person who wont contribute to Qubes docs
because you don’t like to be registered on GitHub. Fair enough. But you
don’t get to use some GitHub tools without being logged in, and advance
search is one of them.

So it’s back to normal search engines. I cant help you with Google
because I really do have some principles, but I showed you how you could
use DDG to find what you wanted.

I hope this will help in the future.

I never presume to speak for the Qubes team.
When I comment in the Forum or in the mailing lists I speak for myself.