How to Properly Search the QubesOS Repository on Github

I tried finding related stuff. But the search mechanism of Github is not super helpful.

These may help:

https://www.qubes-os.org/doc/issue-tracking/#search-tips

1 Like

You are welcome. Thanks for everything else in your post.
I still don’t agree about KeepassXC, but it is important we both brought our arguments so each user can decide for himself.

Thanks, but maybe I wasn’t clear enough: how to get to

via Github search?

Oh, I thought you were asking about searching qubes-issues. That I don’t know. When I try a similar search across the Qubes OS GitHub org, it returns no results. :slightly_frowning_face:

Yes, no global, nor any other search on the term can lead you either to the page, or issue. And it seems even Google search can’t find it. Like it’s buried by Github. And it’s not an exception.

Really?
DDG - Qubes "multifile-policy.markdown" has the spec as #1 and github#4370 as #2
DDG - Qubes multifile-policy has the spec as #1 and github#4370 as #2
Qubes new qrexec policy has Marek’s announcement as #1, with full details

You need to work on your search-fu

1 Like

Is this the question only for me, since @adw couldn’t find it either?
Also

Did you try to click on that link from @marmarek’s opening post supposedly leading to multifile-policy.markdown's page?

It’s 404. No other link from the search

will lead me to qubes-core-qrexec/multifile-policy.markdown at master · QubesOS/qubes-core-qrexec · GitHub too.

That’ why I kindly asked someone to show me how to search on Github and get me to the qubes-core-qrexec/multifile-policy.markdown at master · QubesOS/qubes-core-qrexec · GitHub

Can you, please? It’s a simple question that needs just a link to a search page on a github with the list of results of which at least one should brought me to qubes-core-qrexec/multifile-policy.markdown at master · QubesOS/qubes-core-qrexec · GitHub

No - you said you could not find it with Google either.
You need to work on your search-fu.
If you want to use search you must learn how the search tools work:
user:qubesos extension:.markdown filename:multifile-policy language:Markdown

This isn’t difficult - you can use the “Advanced” search and fill in a
form if you don’t know the right syntax.
The same goes for any of the search engines.
Learn how to use the tools.

I am confused. I tried numerous times. How this will lead me to qubes-core-qrexec/multifile-policy.markdown at master · QubesOS/qubes-core-qrexec · GitHub exactly?

yes, since I couldn’t find it via Github search.

I’m trying, first exploring myself, then asking for help, but can’t get simple answer how to reach qubes-core-qrexec/multifile-policy.markdown at master · QubesOS/qubes-core-qrexec · GitHub

If I use this, I get

Not to say that if I use this on Google, what meaningless results I get

I’m trying, first exploring myself, then asking for help, but can’t get simple answer how to reach qubes-core-qrexec/multifile-policy.markdown at master · QubesOS/qubes-core-qrexec · GitHub via Github search

And agian:

when I manually type it, or choose it via Advanced search, I’m getting

We couldn’t find any repositories matching ‘user:qubesos extension:.markdown filename:multifile-policy language:Markdown’
You could search all of GitHub or try an advanced search.

If i click on Sign in to GitHub · GitHub obviously as you can see I’m getting first to sign in again. Clicking on Avanced search is meaningless, since I came there via Advanced search.

So… where I’m wrong? No, really…

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.

While appreciating your answers and time, it looks you find it proper to discuss this in the same manner in me->you as in you->me direction, while me trying not to allow to obscure basic premise @deeplow stated (your explaining how to get there actually only confirms it, when I’m asked):

Or, you claim it’s super helpful?

OK, at some point you said

like it was right there behind those advanced search terms. When I showed they’re not there, you said:

Really?

For this I didn’t need advanced search. Basic search term multifile-policy.markdown is more than enough to get to /4370, and from there and from what you wrote after that clearly has nothing to do with the search on github, but with the improvisation how to get to there.

Really? And how do you think I actually got the proper link qubes-core-qrexec/multifile-policy.markdown at master · QubesOS/qubes-core-qrexec · GitHub ?

Think! Exactly - that way! Does that actually prove that I think, too? And, more important, is it really how search should supposed to be?

It’s not, as I said above. The link to search all github is asking you to log in, and not the one to search advanced. Advanced search gave no different results than basic search as stated above. Not to say that you actually can search all github even if you’re not logged in. When on /4370 for example and use search from that page, popup allows you to search repository, organization and all github. Jesus, isn’t that super helpful how to get search on all github - go to some repository and search from there whole github. I mean… so Microsoftly.

And that is exactly how Qubes repositories will be lost someday for the devs and us, no doubt. And that is why I don’t want to participate with Microsoft.

At the end, unman shaker search term will lead you directly to the repository, which proves something is so Microsoft with Github.

Because you’re following forum via email, I will correct my previous post to be visible to you. Instead of

it should be

OK, at some point you said

like it was right there behind those advanced search terms. When I showed they’re not there, you said:

@enmus I no longer understand your issue.
You seemed to say that it wasn’t possible to find the page using GitHub
search, or Google.
Now you are saying, “of course I found it”, although there’s a hint at
the end that you think you should be able to do this without thinking.

Your edit doesn’t help - that advanced search on GitHub gives you just one
result
- the page you say cant be found by searching.

All this is wildly off topic for this thread, and seems to be of no
benefit to you. Let’s end it here.

Absolutely agree.
I’m suggesting @deeplow to split the topic to All Around the Qubes, with some topic how to searsh QubesOS repository on Github, or whatever.