unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Vineet Naik <naikvin@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Correct way of overriding custom-set-faces after the color-theme is loaded
Date: Fri, 3 Feb 2012 21:06:24 +0530	[thread overview]
Message-ID: <CADmbCiOmDeKENmcbMZd1Ld+kfhE-pE4vm9ihXNgnde-aLzJp_g@mail.gmail.com> (raw)
In-Reply-To: <87mx90p3tq.fsf@nzebook.haselwarter.org>

On Fri, Feb 3, 2012 at 4:43 PM, Philipp Haselwarter
<philipp.haselwarter@gmx.de> wrote:
> my bad, got confused with my mail accounts.
>
>
> On Fri, Feb 03 2012 09:58 (@1328259509), Philipp Haselwarter wrote:
>
>> two solutions come to my mind:
>>
>> 1) set the face attributes outside of customize, that way they won't be
>>    affected by customize.
>> #+begin_src elisp
>>  (set-face-background 'flymake-errline "DarkRed")
>> #+end_src
>>
>> 2) put custom stuff into a separate file and load that at some point of
>>    your .emacs
>> #+begin_src elisp
>>  (load
>>   (setq custom-file
>>         (expand-file-name "custom.el" user-emacs-directory))
>>   'noerror)
>> #+end_src
>
> Clarification: Do one /or/ the other :) If you choose option two, make
> sure to create the file you set as `custom-file' (C-h v custom-file RET)
> and move all the custom-* stuff from your .emacs into that file. Also,
> use an absolute path-name. If things don't work as expected, remove the
> 'noerror and start emacs as "emacs --debug-init".
>
> --
> Philipp Haselwarter
>
>

Oh! got it now. Your explanantion also helped me refactor my .emacs file :)

Thank you for all the help.

-- 
Vineet Naik



      reply	other threads:[~2012-02-03 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 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=CADmbCiOmDeKENmcbMZd1Ld+kfhE-pE4vm9ihXNgnde-aLzJp_g@mail.gmail.com \
    --to=naikvin@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /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.
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).