Skip to content
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

Color in progress_message #10494

Open
calebmer opened this issue Dec 27, 2019 · 2 comments
Open

Color in progress_message #10494

calebmer opened this issue Dec 27, 2019 · 2 comments
Labels
not stale Issues or PRs that are inactive but not considered stale P3 We're not considering working on this, but happy to review a PR. (No assignee) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: feature request

Comments

@calebmer
Copy link

calebmer commented Dec 27, 2019

Description of the problem / feature request:

As a rule author, progress_message in ctx.actions.run() is one of my primary interfaces with a user of my rule. Perhaps progress_message is the primary interface for users of Bazel in general who don’t spend much time changing build configuration.

Currently, it appears like I can only write plain text for progress_message which isn’t very helpful if I’d like to draw user’s attention to the important parts of the message.

Feature requests: what underlying problem are you trying to solve with this feature?

I’d like, specifically, to bold parts of the progress message that are important and dim parts that are less important.

For example in “Compiling Rust crate proc-macro2” I’d like to bold “proc-macro2” for “Compiling Rust crate proc-macro2”.

I’d like the coloring mechanism to hook into Bazel’s own color option so it can be disabled for shell’s that don’t support color.

@irengrig irengrig added team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: feature request untriaged labels Jan 2, 2020
@philwo philwo added P3 We're not considering working on this, but happy to review a PR. (No assignee) and removed untriaged labels Dec 8, 2020
@sgowroji sgowroji added the stale Issues or PRs that are stale (no activity for 30 days) label Feb 6, 2023
@sgowroji
Copy link
Member

Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so.

@brentleyjones
Copy link
Contributor

I would love this feature as well. Can we reopen it?

@sgowroji sgowroji reopened this Feb 10, 2023
@sgowroji sgowroji added not stale Issues or PRs that are inactive but not considered stale and removed stale Issues or PRs that are stale (no activity for 30 days) labels Feb 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not stale Issues or PRs that are inactive but not considered stale P3 We're not considering working on this, but happy to review a PR. (No assignee) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: feature request
Projects
None yet
Development

No branches or pull requests

5 participants