dj(1): writing/reading should take place at seeked/skipped byte
dj(1): writing/reading should take place at seeked/skipped byte
This seems to have been fixed. #125 adds further clarification. Please reopen if you still have issue.
The original UNIX had a lot of samey names; chmod, chroot, chdir, chsh all come to mind. I can remember them all off the top of my head because they're all intuitive considering their purpose.
0fc9a6b533
Makefile, docs: programmatically generate version for docs (i got tired of doing it myself)
scroll(1) – pager
We only need one pager, the minimal one. I see this as a preference thing, like a text editor: having a minimal text editor is useful, but almost no one prefers the slightly-more-featureful…
This shouldn't have been closed until discussion reached a conclusion.
Why is it less robust? I disagree - this only uses stable Rust features (the code it generates won't be obsoleted) and very elementary Awk features (the empty pattern, print command, and string…
Your fixes for dj(1) are already present in the dj refactor branch, as well as a number of other fixes.