Have Zed cli output logs path to stderr #22509
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cla-bot
bot
added
the
cla-signed
|
I now get this message on every invocation of I think we should revert/refine this. |
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jan 1, 2025
Removes noisy log location stderr output on every `zed` cli invocation. Reverts #22509 Release Notes: - N/A
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: