Ranjan Maitra via Mutt-users wrote: > On Wed Apr16'25 04:54:08PM, Todd Zullinger wrote: >> Testing with pull request #13 does look decent. So it seems >> like the issue may be largely that the theme choice uses a >> bit of a dark background by default, but you can adjust it >> to suite your tastes. [...] > I see, I thought that these pull requests had been > committed and the final product was included here. It > never occurred to me that the "buggy" code is not updated.
That's the thing. One person's bug is another's feature. :)
> Sorry for a very basic question: how do I download this
> corrected pull request file. One way out appears to me to
> be to simply change the "default" to "brightwhite".
There are a number of ways to do that, depending on how
familiar you are with git and whether want to use it for
keeping track of these things.
If you have just downloaded the muttrc theme files manually,
you can do the same thing via the GitHub pull request web
interface. Starting from:
https://github.com/altercation/mutt-colors-solarized/pull/13
Go to the "Files changed" tab and scroll to the file you
want, e.g.: mutt-colors-solarized-light-256.muttrc. Then
click on the '...' at the far right, select "View file"
and then use the "download raw file" option at the top right
of the file (the down arrow icon).
If you already use git to track the mutt-colors-solarized
repos, you can fetch PR #13 within your local clone via:
git fetch origin pull/13/head:pr13
and then switch to it with `git switch pr13` and you'll have
the modified copies of the themes.
Or, you can add .patch to any GitHub pull request and it
will provide the changes in a format suitable for feeding to
git am, e.g.:
https://github.com/altercation/mutt-colors-solarized/pull/13.patch
That can be fetched via curl and fed to git am, e.g.:
curl -L https://github.com/altercation/mutt-colors-solarized/pull/13.patch
| git am
Like the previous method, this also presumes you are
working in a clone of the mutt-colors-solarized git
repository.
> But I was also wondering if there is a better way to
> simply set the default to be something else (instead of
> changing it).
I don't think there is. Using 'default' in the mutt color
scheme is saying "use the default color from the terminal."
If you want to have a light background in mutt in a terminal
with a black background, you should set the color in the
mutt color scheme config.
Beyond that, mutt-colors-solarized-light-256.muttrc doesn't
use 'default' anywhere, so that isn't the real issue there.
It is simply that the colors chosen aren't as light as some
expect. It's not even a bug, just a difference in tastes,
so I can understand why the original author hasn't "fixed"
it.
You can always source the original color scheme and then
override just the few colors you want too, if you think
there will be other changes to those color schemes which you
want to more easily sync and track via git.
--
Todd
signature.asc
Description: PGP signature
