unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
* Correct way of overriding custom-set-faces after the color-theme is loaded
@ 2012-02-03  7:48 Vineet Naik
  2012-02-03  8:58 ` Philipp Haselwarter
  0 siblings, 1 reply; 6+ messages in thread
From: Vineet Naik @ 2012-02-03  7:48 UTC (permalink / raw)
  To: help-gnu-emacs

Hello,

I use the Solarized Dark theme on emacs 23. This theme defines
background color as orange for flymake error line. I wanted to change
this to DarkRed. So in my .emacs file, I added the following lines
after requiring the color theme

;; flymake error and warning faces
(custom-set-faces
 '(flymake-errline ((t (:background "DarkRed"))))
 '(flymake-warnline ((((class color)) (:background "DarkBlue")))))

This was working as expected. Today I set some customization options
using M-x customize-group and saved them due to which, emacs moved the
above lines to the top of the .emacs file resulting in the default
solalized faces to be applied to flymake error.

It also added the following comment under custom-set-faces which is
self explanatory

 ;; If you edit it by hand, you could mess it up, so be careful.
  ;; Your init file should contain only one such instance.
  ;; If there is more than one, they won't work right.

I need to know what would be the correct way to manage my
customizations for the solarized theme without editing the definitions
in the theme itself and make sure they are not overwritten by
customize-*

Thanks
--
Vineet Naik



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2012-02-03 15:36 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-02-03  7:48 Correct way of overriding custom-set-faces after the color-theme is loaded Vineet Naik
2012-02-03  8:58 ` Philipp Haselwarter
2012-02-03 10:11   ` Vineet Naik
2012-02-03 11:04     ` Vineet Naik
2012-02-03 11:13     ` Philipp Haselwarter
2012-02-03 15:36       ` Vineet Naik

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).