I don't think these two comments are necessary, it's apparent what is changing.
find(1p) analogue
Probably nothing like find(1p) which is famously awful (this history lines up with *[A Research UNIX Reader](https://www.cs.dartmouth.edu/~doug/reader.pdf…
docs/scrut.1: write man page for scrut(1)
I decided not to rewrite scrut(1) in Rust because it would still be reliant on libc anyways (as, for example, there's no other way to glean the functionality provided by access(3p)).
Never mind, I looked it up and the HP 41C (basically the gold standard in terms of RPN calculators) is indeed y**x. It looks like Elektronika (which I was referencing, particularly the MK-61…
conv(1) – convert data
Why would one tool do both character encoding conversion and number base conversion?
I figured exponentiating (is that the word?) x to the power of y (Python: x ** y) would be more intuitive for existing RPN users (because this matches the operation on HP and Elektronika…
qi(1): The qi shell
Goodness... I think that would be a vector implementation. I don't know how to feel about it now.
Our flow control is still up in the air so ignore the weirdness besides let and def:
qi(1): The qi shell
On second thought def when used without arguments should display variable usages. Here are some examples of its use to help explain it.
First let's set some variables:
; let a b
;…qi(1): The qi shell
emma and i were discussing variable assignment and the potential usage of a
letterm, which is used to define terms. some pseudoishcode snippets from the conversation to elucidate on that a…
qi(1): The qi shell
Perhaps there should be a way to change which file is used for randomness, in the shell. Like a random_source variable that expands to a file (like /dev/random).
This could potentially be…
mix(1) – randomly sort inputs
Maybe shuffle?
Then you could do stuff like `for f in /media/audio/*; do scrut -f "$f" && out "$f"; done
qi(1): The qi shell
Accidentally tapped the button. That thought's incomplete and I'll finish it later.