2 <p>The jump box (the little text box with the 'Jump' button by its side) has two functions.
4 <h2>Direct ID jump</h2>
6 If you enter an ID and press Jump (or Enter), you are sent directly to that ID.
8 The ID can be either an absolute path (with segments separated by slashes
9 and/or colons). The exact rules for matching the paths are as follows, but
10 maybe you want to see the examples at the end of this page first.
12 If the ID starts with an ID type prefix (e.g., 'PC'), it is considered absolute.
14 If it starts with a segment separator, it is considered absolute inside current ID tree (e.g., PCI devices).
16 Otherwise, it is relative and it is appended to the current ID, then to its parent and so on,
17 until an existing entry or the root of the tree is reached.
19 If the absolute address is not found, we try to interpret it as relative instead.
23 If the direct ID jump does not succeed, we search entry names for the given string.
24 By default, only names of the same ID type are searched (if you browse PCI devices, you will not get results from device classes).
25 If you want to search all names, prefix the search with an asterisk ('*').
27 If you want to turn off name search in your query, prefix the query with '#'.
31 All examples are searches from within ID 'PC:0000:0000'.
33 <li><tt>PD:00</tt> ‒ jumps to <tt>PD:00</tt> (PCI class <tt>00</tt>), if it exists.
34 <li><tt>:1234</tt> ‒ jumps to <tt>PC:1234</tt> (PCI device vendor <tt>1234</tt>), if it exists.
35 <li><tt>abcd</tt> ‒ tries <tt>PC:0000:0000:abcd</tt>, then <tt>PC:0000:abcd</tt>, then <tt>PC:abcd</tt>. Then searches in names.
36 <li><tt>#abcd</tt> ‒ same as above, but does not switch to searching in names.
37 <li><tt>Some text</tt> ‒ all ID searches will fail, so names of PCI devices are searched for <tt>Some text</tt>.
38 <li><tt>*Some text</tt> ‒ same, but the search is through all items in the database.