261029.4 · 00011b6688dc6372821c09b0a62727dbb8effcb3
A search's recent pages come only from the page's own tree
Recent pages crossed trees, so on the web address a search in one repo listed pages from repos read before. Each page's search box now names its tree, and each stored entry keeps the tree it was opened in. A version counts as its tree. Entries stored before this have no tree and are dropped.
reading declarations
Changes to doc/pages.md. All files
@@ -40,7 +40,7 @@ The list arrives after the page, since the server walks the tree for it: a few m ## Recent pages -The browser remembers the pages you open; the server keeps no such list. A search shows the best five that match its words first, under recent, from any tree on the address.+The browser remembers the pages you open; the server keeps no such list. A search shows the best five that match its words first, under recent. They come from the tree you are in, so one repo's reading never shows in another's. A version counts as its tree. Each visit counts and recent visits weigh more, as in zoxide. A reload is no visit.