From: Mauro Aranda <maurooaranda@gmail.com>
To: Christoph <cschol2112@gmail.com>
Cc: 16298@debbugs.gnu.org
Subject: bug#16298: 24.3.50; Customize settings for color scheme don't take effect
Date: Thu, 5 Nov 2020 20:56:26 -0300 [thread overview]
Message-ID: <CABczVwdjU7bZP7o7z0jZH1v=_-PXNrfmUx1-5jiyk1sYfSgm6Q@mail.gmail.com> (raw)
In-Reply-To: <877gan9hem.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
close 16298
quit
Mauro Aranda <maurooaranda@gmail.com> writes:
> Christoph <cschol2112@gmail.com> writes:
>
>> I am using a custom colorscheme (solarized-theme from marmalade
>> repo). It is configurable via `customize' to affect font sizes etc.
>>
>> When configured via `customize' the settings don't have have any
>> effect. I verified the variable values manually with `C-h v' and it
>> shows the values have been changed to the expected values. The behavior
>> of the color scheme does not reflect the new values though.
>>
>> When configuring the settings by explicitly setting them via `setq' in
>> my `init.el' the color scheme behaves correctly.
>>
>> Is there possibly an issue with the order of enabling color schemes and
>> loading settings?
>>
>
> Hello Christoph.
>
> Unfortunately, your bug report didn't get an answer when you reported
> it.
>
> Has something like this happened lately? We would need more information
> to proceed with this bug report.
This was 2 months ago, and there was no response. Without more
information, it doesn't seem possible to make progress with this bug
report so I'm closing it. If this is still an issue, reply to this
email CCing 16298@debbugs.gnu.org and we can reopen the bug, if needed.
[-- Attachment #2: Type: text/html, Size: 1667 bytes --]
prev parent reply other threads:[~2020-11-05 23:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 2:55 bug#16298: 24.3.50; Customize settings for color scheme don't take effect Christoph
2020-09-04 21:02 ` Mauro Aranda
2020-11-05 23:56 ` Mauro Aranda [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABczVwdjU7bZP7o7z0jZH1v=_-PXNrfmUx1-5jiyk1sYfSgm6Q@mail.gmail.com' \
--to=maurooaranda@gmail.com \
--cc=16298@debbugs.gnu.org \
--cc=cschol2112@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).