Reading a page

Scrolling is smooth: it glides to where you are going instead of jumping. How fast it catches up is a setting (Scroll speed: slow, normal, fast), and Smooth scrolling off makes it instant.

Going somewhere in a long page. t opens the section index, which is the fastest way around: documentation, long articles and API references all get read top-down with ] and [, or selectively with t.

Code blocks are highlighted by language and shown in a labeled frame with the language name on the border. The language comes from the page (language-xx classes, data-language, and the conventions of Sphinx and MediaWiki). When a site ships no language at all — build-time highlighters such as Shiki leave only colored spans — wr infers it, but only when one language clearly wins over the others among Go, Python, JavaScript, TypeScript, JSON, Bash, SQL, Rust, Java and C#, and it says so on the frame (go (guessed)). A block it is not sure about stays in plain color, because a wrong color is worse than none. Guess code language off keeps only what the page declares, and Code frames off removes the label and frame if you want the page tighter.

What is left out. Besides menus, footers and cookie walls, wr drops what the page itself hides (the hidden attribute, display:none), permalink anchors in headings (¶, #), “skip to content” links, the navigation strips that sit above a title (breadcrumbs, section labels, Next:/Up:), and empty links. A link that wraps a title and a description (a card) shows the title as the link and the description under it.

Width. By default the text column is 100 columns wide and centered, which is comfortable to read on a wide terminal. Reading width in Settings offers the usual widths plus full for the whole terminal.