- https://tebibyte.media/~emma
-
fae/faer
- Joined on
2022-02-27 -
-
49a3bb9f30
Makefile, .gitignore, .editorconfig, configure, tests/cc-compat.sh: added configure script for compiler optimizations
After going over this with Trinity verbally, we have decided to merge the existing fop(1) implementation while we work on resolving #19.
I suppose we need to resolve #19 before we can truly decide on what to do.
I’m not exactly sure what the best way to go about this would be. I didn’t see this before adding the -d option.
49a3bb9f30
Makefile, .gitignore, .editorconfig, configure, tests/cc-compat.sh: added configure script for compiler optimizations
qi(1): The qi shell
Its definition in POSIX makes it unintuitive for shell scripters. Emma should elaborate here when fae has time, fae has more experience with this.
From: "Lawrence Velázquez" <vq@larryv.m…qi(1): The qi shell
Maybe we could have a shift-like that will “shift” any variable with IFS-delineated text?
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.
shift(1)…
yes(1) analogue
i think we discussed an out(1) command in the past that does what echo does but without the uncertainty that comes with how it’s defined in POSIX. we definitely want a format(1) command but i…
Sounds good. We should get started when we have a few more of our own utilities to show for it
yes(1) analogue
i didn’t think we would be including printf? didn’t we discuss a different formatting tool?
that’s true. it could probably be both in the README and the Makefile as a comment