REDO-ALWAYS(1)

💅 REDO-ALWAYS(1) — the redo-always glow-up 🎀

okay so bestie, welcome to the redo-always page from the General Commands Manual — it's short, it's iconic, it's giving "small but mighty" ✨

🌸 NAME

redo-always — marks the current redo target as always needing to be rebuilt 💫

🦋 SYNOPSIS

redo-always

that's it. no flags, no args, no drama. periodt. 💅

💖 DESCRIPTION

so redo(1) is this whole tool for building files and then rebuilding them whenever any of their dependencies have changed — king behaviour, honestly 👑.

redo-always, when you invoke it from inside a dofile, adds a dependency on the current target that is literally impossible to satisfy. like, not "hard", not "eventually" — impossible 🫶. the result? the target gets rebuilt every single time if you pass it as an argument to redo-ifchange(1). forever. no cap. 🔥

✨ EXAMPLES

okay so picture these three dofiles, all.do, b.do and c.do — a whole little ecosystem 🧚:

all.do

#!/bin/sh
redo-ifchange b

b.do

#!/bin/sh
redo-ifchange c
sleep 1
date +%s

c.do

#!/bin/sh
redo-always
date +%s

now if you invoke redo(1) in a directory that has these three files, it'll build a file named c containing a timestamp, and a file named b containing a timestamp that is at least one second later ⭐.

and both b and c will always be rebuilt whenever you invoke redo(1) — because the default target all depends on b, which in turn depends on c, which is carrying that impossible-to-satisfy dependency like the main character it is 💀👑

🌈 HISTORY

redo-always was designed by Avery Pennarun as part of his redo implementation, and implemented by Ælla Chiana Moskopp. collab of the century, honestly 🫶💜

🎀 AUTHOR

redo-always and this man page were written by Ælla Chiana Moskopp. writing the tool and then writing the docs about the tool? that's called range, bestie ✨

💜 COPYRIGHT

Copyright © 2014-2016 Ælla Chiana Moskopp. License AGPLv3+: GNU Affero GPL version 3 or later <http://www.gnu.org/licenses/agpl-3.0.html>.

This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. (read that again: NO WARRANTY. absolutely none. 😭)

🍓 SEE ALSO

redo(1), redo-dot(1), redo-ifchange(1), redo-ifcreate(1), redo-ood(1), redo-sources(1), redo-stamp(1), redo-targets(1) — the whole friend group, go say hi 💖

🙈 BUGS

heads up bestie: redo-always may break if the target filename contains a tab or a newline. like. genuinely. don't do that 💀

---

and that's the page! this was REDO-ALWAYS(1) from the General Commands Manual — go build something and let it rebuild itself forever, you absolute icon 🦋💅🌸