Visitar URL original
set_color: list valid color aliases by adamjstewart · Pull Request #13062 · fish-shell/fish-shell · GitHub
Skip to content

set_color: list valid color aliases - #13062

Open
adamjstewart wants to merge 9 commits into
fish-shell:masterfrom
adamjstewart:docs/set-color
Open

adamjstewart wants to merge 9 commits into
fish-shell:masterfrom
adamjstewart:docs/set-color

Conversation

@adamjstewart

@adamjstewart adamjstewart commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Stumbled upon a few valid color options that were not previously documented in https://fishshell.com/docs/current/cmds/set_color.html.

Happy to sort these alphabetically, by rainbow color spectrum, or whatever you prefer. For now I kept them in the same order as other files.

TODOs:

  • If addressing an issue, a commit message mentions Fixes issue #<issue-number>
  • Changes to fish usage are reflected in user documentation/manpages.
  • Tests have been added for regressions fixed
  • User-visible changes noted in CHANGELOG.rst

Signed-off-by: Adam J. Stewart <ajstewart426@gmail.com>
@krobelus

krobelus commented Oct 22, 2026 via email

Copy link
Copy Markdown
Contributor

@adamjstewart

Copy link
Copy Markdown
Contributor Author

Is brown equal to yellow or is that only in my settings?

@krobelus

krobelus commented Oct 22, 2026 via email

Copy link
Copy Markdown
Contributor

Signed-off-by: Adam J. Stewart <ajstewart426@gmail.com>
Signed-off-by: Adam J. Stewart <ajstewart426@gmail.com>
Signed-off-by: Adam J. Stewart <ajstewart426@gmail.com>
@adamjstewart

Copy link
Copy Markdown
Contributor Author

FYI this is my first time in Rust so please double check I didn't do anything stupid. Let's see if the tests pass, not sure if these attributes are used anywhere else in the code...

Signed-off-by: Adam J. Stewart <ajstewart426@gmail.com>
Signed-off-by: Adam J. Stewart <ajstewart426@gmail.com>
Signed-off-by: Adam J. Stewart <ajstewart426@gmail.com>
Signed-off-by: Adam J. Stewart <ajstewart426@gmail.com>
Comment thread crates/color/src/lib.rs Resolved
Signed-off-by: Adam J. Stewart <ajstewart426@gmail.com>
@adamjstewart adamjstewart changed the title Docs: set_color list all valid colors set_color: list all valid colors Oct 23, 2026
@adamjstewart adamjstewart changed the title set_color: list all valid colors set_color: list valid color aliases Oct 23, 2026
@Nahor

Nahor commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

You should squash some of those commits. The history doesn't need to keep track of every silly mistakes, missed formatting, and whatnot. It makes the git history harder to read, git blame less informative, and reverting changes more painful.
There should be only 2, maybe 3, commits here:

  • the doc update
  • the removal of _rgb and hidden
  • maybe the +1 for the capacity, but since it's such a minor change, it could be squashed with the field removal.

As for the change itself, I think it would be better if set_color --print-colors put the identical colors on the same line. As-is, if one doesn't read the documentation, one might wonder what the difference is between, say yellow and brown, especially since the way the brain interprets color is very context sensitive (i.e. the yellow and brown might appear slightly different) 1

Footnotes

  1. heck, it may even be different because of a monitor's localized backlighting ↩

@adamjstewart

Copy link
Copy Markdown
Contributor Author

You should squash some of those commits.

Could also do this automatically when merging the PR, less work for everyone.

I think it would be better if set_color --print-colors put the identical colors on the same line.

That might be beyond my current level of Rust abilities...

@Nahor

Nahor commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

You should squash some of those commits.

Could also do this automatically when merging the PR, less work for everyone.

How would an automated system know which commits to squash together? That only works if the goal is to squash everything into a single commit, not in 2 or 3.

And, put bluntly, you created that mess of commits in the first place, some of which don't even compile! And now you're asking someone else to fix some basic commit hygiene issues that shouldn't have existed in the first place?

@adamjstewart

Copy link
Copy Markdown
Contributor Author

I'm fine with 1 commit or 3 separate PRs if that makes more sense. Most repos I contribute to only do squash merges. This is also my first time writing Rust, so apologies for the messy history.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants