Bug 2503680 - Bash Color Prompt 1.0
Summary: Bash Color Prompt 1.0
Keywords:
Status: MODIFIED
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jens Petersen
QA Contact:
URL:
Whiteboard:
Depends On: 2513913
Blocks: F46Changes
TreeView+ depends on / blocked
 
Reported: 2026-07-21 15:37 UTC by Aoife Moloney
Modified: 2026-09-17 05:24 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:
fedora-admin-xmlrpc: mirror+

Attachments (Terms of Use)

Description Aoife Moloney 2026-07-21 15:37:58 UTC 
This is a tracking bug for Change: Bash Color Prompt 1.0
For more details, see: https://fedoraproject.org/wiki/Changes/BashColorPrompt_1.0

bash-color-prompt (bcp) version 1.0 is a rewrite of Changes/Color_Bash_Prompt (introduced in Fedora 39) with a new cleaner simple design, which uses bash PROMPT_COMMAND to update dynamic customized prompts. The default system prompt (still green and static) is much simpler now and there is only one predefined function, which enables optional customization.

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.
Comment 1 Jens Petersen 2026-09-09 07:04:01 UTC 
So this finally landed in Rawhide yesterday, after fixing some late discovered regressions (I was away for 2 weeks).

I guess I am worrying that it might be late to push this to F45 now?
Though waiting another 6 months will only reduce the amount of testing it gets in the near term.
Comment 2 Jens Petersen 2026-09-15 07:36:34 UTC 
Probably makes the best sense to move this to F46.
That will also give a little more time for refinements, improvements, and polishing.
Comment 3 Aoife Moloney 2026-09-16 11:23:13 UTC 
Ack, moving to F46.
Comment 4 Jens Petersen 2026-09-17 05:24:05 UTC 
Okay, thanks!

Moving to Modified since the package is already available in Rawhide.
Note You need to log in before you can comment on or make changes to this bug.