-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are already executed commands no longer colored? #4966
Comments
Hi @gp0119 I think this may be intentional, but when I went as far back as Jan 2023 build and didn't see the colors on the output for commands. Do you know when or which version you saw with this behavior? |
@dannyneira hi, can you tell me where I can download previous versions? I'm quite sure the earlier version had colors. perhaps you could try version 2024.05.16 (v0.2024.05.14.08.01). |
@dannyneira I downloaded version v0.2024.05.14.08.01.stable_04 and found that previously executed commands are colored. |
@gp0119 I see, this isn't the same by default and there is no setting for that so by any chance do you have any plugins in your rc file that modify colors? ( |
I didn't use any plugins that change colors. Strangely, I upgraded to the latest version again, and the colors have returned. |
hm strange. I'll close for now, but if it happens again please let us know and provide copy of your rc files (with no secrets included). |
Dupe Check
Describe the bug
Since the recent update, I noticed that previously executed commands are no longer colored. Is this intentional?
To reproduce
Expected behavior
No response
Screenshots
No response
Operating system
MacOS
Operating system and version
MacOS 14.5
Shell Version
No response
Current Warp version
No response
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
No
Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)
Yes, this I confirmed this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None
The text was updated successfully, but these errors were encountered: