Print events right after spawning when --why and --clear are used tog…

…ether (#198)

src/config/runtime.rs

@@ -153,7 +153,7 @@ pub fn runtime(args: &Args, command_order: Vec<&'static str>) -> Result<RuntimeC
 	config.on_action(move |action: Action| {
 		let fut = async { Ok::<(), Infallible>(()) };
 
-		if print_events {
+		if print_events && !clear {
 			for (n, event) in action.events.iter().enumerate() {
 				eprintln!("[EVENT {}] {}", n, event);
 			}
@@ -304,6 +304,16 @@ pub fn runtime(args: &Args, command_order: Vec<&'static str>) -> Result<RuntimeC
 				.show()?;
 		}
 
+		// with --clear, printing the events right before clearing is useless.
+		// this way is a bit incorrect as we'll print before every command, but
+		// it will be actually useful. Perhaps this warrants a new Watchexec hook
+		// for post-outcome or mid-outcome...
+		if print_events && clear {
+			for (n, event) in postspawn.events.iter().enumerate() {
+				eprintln!("[EVENT {}] {}", n, event);
+			}
+		}
+
 		#[cfg(target_os = "freebsd")]
 		return Ok::<(), Infallible>(());
 		#[cfg(not(target_os = "freebsd"))]