You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In theory it is possible to build a more complex query for querying a particular search engine
As an illustration, let's say gmail example, where !gmail hello searches gmail for hello.
The url pattern of gmail, when there are multiple users are logged in gmail at the root url is https://mail.google.com/mail/u/0/#inbox, where in mail/u/0/#inbox:
mail is a root prefix that does not seem to change across the mail app
u is a prefix for saying there are multiple user accounts that are used on this browser and terminal (maybe, see next point)
0 is the local id of the stored user (probably in local storage etc). If you open your second inbox you'll see that number becoming 1
#inbox is some sort of query param that is bound to the search input, but not just to simple search, to a more advanced boolean search in:inbox, or is:draft for #draft
This seems to be very similar on Google Drive too.
The only new thing in these examples, is the second level of bang !, which would be the thing that has to be investigated and defined in feature design.
The text was updated successfully, but these errors were encountered:
In theory it is possible to build a more complex query for querying a particular search engine
As an illustration, let's say gmail example, where
!gmail hello
searches gmail for hello.The url pattern of gmail, when there are multiple users are logged in gmail at the root url is https://mail.google.com/mail/u/0/#inbox, where in
mail/u/0/#inbox
:mail
is a root prefix that does not seem to change across the mail appu
is a prefix for saying there are multiple user accounts that are used on this browser and terminal (maybe, see next point)0
is the local id of the stored user (probably in local storage etc). If you open your second inbox you'll see that number becoming 1#inbox
is some sort of query param that is bound to the search input, but not just to simple search, to a more advanced boolean search in:inbox, or is:draft for #draftThis seems to be very similar on Google Drive too.
Therefore we can imagine a find queries such as:
!gm !u1 is:draft hello
searching on my gmail personal account for a hello draft message https://mail.google.com/mail/u/1/#search/in%3Adraft+hello!drive !u0 type:pdf contract
searching my gmail professional account for contract of type pdf https://drive.google.com/drive/u/0/search?q=type:pdf%20contractThe only new thing in these examples, is the second level of bang
!
, which would be the thing that has to be investigated and defined in feature design.The text was updated successfully, but these errors were encountered: