From e9bd4b2890d7ef4bc9cc88eef649a49ffdf53e86 Mon Sep 17 00:00:00 2001
From: Michael Sloan <michael@zed.dev>
Date: Mon, 30 Dec 2024 14:14:08 -0700
Subject: [PATCH] Have Zed cli output logs path to stderr (#22509)

When switching from just running the editor directly to using the CLI I
missed the logs in the terminal and started using `--foreground`. I
realized this was because there was a tiny amount of effort involved in
finding out where logs were being written to. Having the cli output it
to stderr helps make this more visible.

Seems like such a minor thing not listing in release notes.

Release Notes:

- N/A
---
 crates/cli/src/main.rs | 1 +
 1 file changed, 1 insertion(+)

diff --git a/crates/cli/src/main.rs b/crates/cli/src/main.rs
index 3dbfa0e737..1e48a16c07 100644
--- a/crates/cli/src/main.rs
+++ b/crates/cli/src/main.rs
@@ -257,6 +257,7 @@ fn main() -> Result<()> {
     if args.foreground {
         app.run_foreground(url)?;
     } else {
+        eprintln!("Logs are written to {:?}", paths::log_file());
         app.launch(url)?;
         sender.join().unwrap()?;
         pipe_handle.join().unwrap()?;