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.

Some of my configuration files are online aren’t they? Raku is one of the most interesting, if not the most. I’m not an expert but it pretty much has every language construct (e.g promises) plus exotic stuff. The exotic operators are strangely intuitive (and “hyped”).

my @bin = 1..3;
@bin>>++;
say @bin;

I use it for quick CLIs with the multi dispatch CLI feature. The logo is a butterfly (or maybe it’s a raccoon).

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”.

The nmap command can enumerate SSL ciphers on the server.

nmap --script ssl-enum-ciphers -p 443 domain.example

The SSL Labs’ SSL test is similar? In debugging purgatory, there are instances where declarations in a configuration do not translate into reality and it’s not always the implementation, or the server, but sometimes exotic interactions between systems.

A quick wrapper script for normalized git commit dates. Commit dates and timezones are normalized or truncated to the day. This is useful for avoiding rebasing and/or not having to think about system or git date/time settings when on another device or in another timezone. If precise timestamps matter, then it is easily disabled.

#!/bin/sh -eu

GIT=$(which git --all | grep --invert-match "local/bin" | head --lines 1)
GIT_COMMITTER_DATE="$(date --utc --date '0' '+%a %b %d %H:%M:%S %Y %z')"

export GIT_COMMITTER_DATE

[ "${1:-}" = "commit" ] && export DATE=1 && $GIT "$@" --date="$GIT_COMMITTER_DATE"

[ "${DATE:-}" = 1 ] && exit

$GIT "$@"

Infinite scrolling is unusual. Most implementations are “almost infinite” to avoid excessive DOM length (memory).

• Infinite scrolling: Limits content to an arbitrarily large amount to avoid exhausting memory.

• Virtual scrolling: Unload everything except the visible viewport + a top and bottom offset. Pad the rest.

Virtual scrolling is infinite, but breaks auxiliary actions ( CTRL + F ) because what’s on the screen is the content.

document.addEventListener("scroll", function() {
  console.log(document.querySelectorAll('*').length)
});

The most popular library appears to be https://infinite-scroll.com.