Konrad Hinsen @khinsen.net · 03/05/2026Hmmmm... Makes sense, but there is nothing obvious for that purpose: 100
Konrad Hinsen @khinsen.net · 24/09/2025Question to Linux experts: Where does this weird pop-up come from that I get whenever pressing a deadkey on my keyboard? How can I disable it? I see this since I updated from Debian 12 to Debian 13. I see it only in a few programs, such as xterm and Emacs, where it often covers text I need to see. 110
Konrad Hinsen @khinsen.net · 16/04/2025Executable examples are another way to guide readers to understanding code. A small Play button allows immediate execution and inspection of the result. #metasci 100
Konrad Hinsen @khinsen.net · 16/04/2025In HyperDoc, the code is an integral part of a hypertext web. You can insert links to the documentation from the code itself. Readers are able to freely navigate from code to text and from text to code. #metasci 100
Konrad Hinsen @khinsen.net · 16/04/2025However, the implementation is only one click away. Readers can also explore the data with their own code in the Playground. But note that the Playground is disabled in the demo for security reasons. You have to install HyperDoc on your own computer to get the Playground. #metasci 100
Konrad Hinsen @khinsen.net · 16/04/2025When presenting data, you can provide multiple relevant views on it, to guide the reader to what you see as important. #metasci 100
Konrad Hinsen @khinsen.net · 16/04/2025Code contains scientifically relevant choices, but also tons of technical details. With HyperDoc, you isolate the science into short functions and transclude them into your prose. #metasci 100
Konrad Hinsen @khinsen.net · 16/04/2025The most important design principle behind HyperDoc is "don't hide anything". Neither scientific details nor implementation details. If a message risks being drowned in details, move them out of the way. Hypertext can do this, unlike the linear narratives of computational notebooks. #metasci 100