The interest in TUIs online is high. In the real world you tend to be constrained and blindfolded by the tools available/allowed. Filtering is peculiar though.

See how the terminal/editor splits? Filtering makes them kiss? Commands that input|output (pipe) work best (compilers, transpilers and code generators). The meta is the limit.

File name, spelling, and dictionary completion exist too. This is tortured, but combining them makes a meta point? The “meta” is hard to convey, but completion doubles as a way of finding, changing, and passing keywords around. Terminals are fair game too. That’s basic completion in a nutshell (minus the magic).

Command line completion is probably another lesser known one. The command line window is minimized, but typing q: (commands) and q/ or q? (search forward/backward) opens it up completely. Wild mode configures its behaviour.

Abbreviations are another completion primitive in Vim. Since it’s full auto, it wants to be magical. <Key> presses and scripts can be replayed. Paired with custom completions and output from external tools, it transforms into advanced witchcraft and/or cursed sorcery. In my case, it just expands acronyms.

Here’s Vim editor thesaurus completion. This kind of completion has its various limitations that I might detail later. I mentioned thesauri in passing but my Internet connection is pitiful and writing about editor meta feels a bit bizarre.

More Vim editor meta? Since posting a video of my LaTeX/Vim shenanigans, queries for tips arrive occasionally. Completion and whole line completion are boilerplate hammers. The more buffers and windows loaded, the more “robust”.

Banana trees are kind of invincible. Here’s what happens if you chop a sufficiently radioactive one clean across the mid…

The Chrome experimental recorder tool has been around for a long while. I thought it was still mostly wip but I got schooled and apparently, this is a more faster way to jump–start a puppeteer script/test:

Which browser engine “paints” HTML the smartest on my device? In the clip below; Surf substitutes for Safari and Chromium for Chrome. My blog is the testee since there’s guaranteed cache control and jitter.

Surf and by extension Safari (or any Webkit–based browser) wins imo. Webkit feels smooth (sneakily, too smooth). It’s probably partly why Safari on macOS/iOS feels so fast. Chrome (not Chromium) is almost on par or so I’ve been told. Not exactly web dev but interesting huh?

Strange. In the last few years, I’ve abandoned search engines for most programming related queries by chugging along happily with Recoll. If I had the time I’d sit down and hack out a web front–end for its Python API but the desktop interface supplied with HTML from my own web crawlers works beautifully (medoc92/recollwebui also exists).