REDO-LOG(1)

💅 redo-log — like, the actual manual page, bestie

okay so this is redo-log(1), from the User Commands girlies ✨

---

🌸 NAME 🌸

redo-log — display log messages from previous builds. that's it. that's the whole vibe check 🫶

---

🎀 SYNOPSIS 🎀

redo-log [options...] [targets...]

literally just options and targets, go off 👑

---

🦋 DESCRIPTION 🦋

okay so listen. when redo runs, it captures the standard error (stderr) output from the build activity for each target, and saves it for later. like a little diary for your build bestie 📓✨

and when a target is rebuilt? the new logs replace the old logs for that target. out with the old, in with the new, no cap 💅

redo-log prints the log output for any set of targets. that's the whole job. main character energy fr

---

✨ OPTIONS ✨

• -r, --recursive — if the requested targets cause any dependencies to be built, recursively show the logs from those dependencies as well. (and if those dependencies build further dependencies, also show those logs, and so on. it's giving inception 🌀)
• -u, --unchanged — show messages even for dependencies that were unchanged (did not need to be rebuilt). to do this, we show the logs for the most recent build of each affected dependency. usually this is used with -r. like, we're showing you the old receipts too, bestie 🧾
• -f, --follow — if a build is currently running for any of the requested targets or their dependencies, follow the logs (like tail -f) until the build finishes. you're just standing there watching it happen 👀
• --no-details — display only the messages from redo itself, not the other messages produced by build scripts. generally this gives you a list of which targets were built, but not detailed logs, warnings, or errors. the tl;dr of the tl;dr 📋
• --no-status — don't display the running build status at the bottom of the screen. (unless this option is specified, the status line will be enabled if using --follow, if stderr is a terminal.) if stderr is not a terminal, you can force enable the status line using --status. so yeah, there's a --status too, iykyk 🌈
• --no-pretty — display "raw" redo log lines (@@REDO events) rather than using a human-readable format. the default is --pretty. raw mode is for the girlies who read hex for fun 💀
• --no-color — when using --pretty and writing to a terminal, colorize the output to make results stand out more clearly. if not writing to a terminal, you can use --color to force colorized output. yes, --color exists, it's literally the inverse, obsessed 🌈✨
• --debug-locks — print messages about acquiring, releasing, and waiting on locks. because redo can be highly parallelized, one instance may end up waiting for a target to be built by some other instance before it can continue. if you suspect this is causing troubles, use this option to see which instance is waiting and when. detective mode fr 🔍
• --debug-pids — add the process id of the particular redo instance to each output message. this makes it easier to figure out which sub-instance of redo is doing what. name tags for your processes 🏷️

---

🧚 REDO 🧚

part of the redo(1) suite. found family, honestly 🫶

---

👑 CREDITS 👑

the original concept for redo was created by D. J. Bernstein and documented on his web site (http://cr.yp.to/redo.html). this independent implementation was created by Avery Pennarun and you can find its source code at http://github.com/apenwarr/redo. legends only, we stan 💖

---

⭐ SEE ALSO ⭐

redo(1) — go read it, bestie, it's right there

---

🍓 AUTHOR 🍓

Avery Pennarun <apenwarr@gmail.com> — thank you for your service 🫡💜

---

Redo 0.42d, dated 2021-07-27 — ok that's the whole page, you're officially smarter than everyone in the group chat now, slay 🎀💅✨