fis(1) – field isolator
(-d delimiter) shouldn't be limited to one byte. cut -d " - " should be possible.
POSIX dd(1p) does this:
sync Pad every input block to the size of the ibs= buffer, appending null bytes. (If either block or unblock…
While we have agreed to "use ASV", I have yet to see any discussion of what that practically means. How will ASV be used? [USAS X3.4-1968](https://ia800800.us.archive.org/35/items/enf-ascii-196…
qi(1): The qi shell
It necessitates storing "$0" as a new shell variable to be able to continue using it, which shell authors writing diagnostics messages and following good practice always want to do.
…
qi(1): The qi shell
I don't like the shell built-in shift.
- It seems to mainly exist as an equivalent to the C idiom
++argv; --argc;which is (given the benefit of >30 years of hindsight since C89) a…
yes(1) analogue
Emma and I just discussed this:
format(1) should be a string formatter akin to printf(1p) but without sucking. out(1) should be a wrapper around format(1) to be an echo(1) equivalent without…
Busybox dd(1) doesn't count skipped records written as nuls in its statistics output. Given the use of the phrasing "before copying" I think this is fine.
Busybox dd(1) fails to seek on streams because lseek(3) returns -1 and sets errno to 29, "Invalid seek". I don't think this follows POSIX, which says the following:
seek=n Skip n…
I just noticed dd(1p) specifies that seek=100 and skip=100 seek/skip 100 blocks, not bytes. I'm not replicating that behavior because it sucks.
yes(1) analogue
printf(1p) would be a nice addition.
On second thought I might be able to implement it in shell without terrible hacks. It seems to do the following:
- Printing verbatim. This can be…
yes(1) analogue
printf(1p) will suck to implement so I'll wanna finish what I've already done before that.
yes(1) analogue
Here's a fully featured yes(1) in C:
#include <stdio.h> /* fprintf(3), NULL */
#include <stdlib.h> /* stdout */
#include <sysexits.h> /* EX_OK */
char *fake_argv[] = {
(char [])…
yes(1) analogue
echo -r, -r being "reverberate", would be delightful, but echo(1p) is implementation dependent enough as-is.
speak has historically been used for text-to-speech, so maybe not the best…
Is it necessary to make another file? A section listing system distributions' package managers' dependencies for running make wouldn't be too long.
I'd like a separate project for each POSIX section 1 utility to implement all the defined functionality.