From: Liang Wang <netcasper@gmail.com>
To: Jonathan Rockway <jon@jrock.us>
Cc: emacs-devel@gnu.org
Subject: Re: emacs --daemon and X faces becoming "unspecified"
Date: Sat, 7 Feb 2009 15:45:59 +0800 [thread overview]
Message-ID: <a161d0b60902062345u5d787babyb1c6385c262a3833@mail.gmail.com> (raw)
In-Reply-To: <87ocxg6ko9.fsf@bar.jrock.us>
On Fri, Feb 6, 2009 at 4:20 PM, Jonathan Rockway <jon@jrock.us> wrote:
>
> Hi all,
>
> I've recently started using emacs --daemon + emacsclient -c as my
> primary means of interacting with emacs. Generally, it works great, but
> I have noticed that I can no longer set the default face via custom.
>
> In my custom-set-faces section, I have a line that looks like:
>
> '(default ((default (:stipple nil :background "black" :foreground
> "gray90" :inverse-video nil :box nil :strike-through nil :overline nil
> :underline nil :slant normal :weight normal :height 72 :width normal
> :foundry "bitstream" :family "Bitstream Vera Sans Mono")) (nil nil)))
>
> The key is that "background" is black. I do indeed get a black
> background, but if I view the default face in custom, custom thinks the
> background is "unspecified-bg". If I change this to something else and
> set or save the custom face, emacs goes into an infinite loop. (I can
> provide more details about this; C-g doesn't kill it, though.)
>
> Everything else generally works OK, except occasionally I get
> messages like ``Unable to load color "unspecified-bg" [6 times]'' in
> *Messages*. This doesn't seem to be causing any malfunction, though.
>
> Finally, if I just run "emacs" normally (not emacsclient -c), everything
> works fine. The color is "black" in customize, I don't get warning
> messages, and I can change the color and set/save.
>
> Anyway, any pointers on where to look for the cause of this would be
> appreciated. It doesn't seem to be a very critical problem, but it
> would be nice to understand what's causing it.
>
> Regards,
> Jonathan Rockway
>
> --
> print just => another => perl => hacker => if $,=$"
>
>
>
I had same issue before.
After I move almost all of other customization below custom-set-faces
in .emacs file, this problem is gone. I don't know why. :-)
Liang
prev parent reply other threads:[~2009-02-07 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 8:20 emacs --daemon and X faces becoming "unspecified" Jonathan Rockway
2009-02-06 18:48 ` X faces becoming "unspecified" with emacs -nw when creating an X11 frame (was: Re: emacs --daemon and X faces becoming "unspecified") Dan Nicolaescu
2009-02-07 7:45 ` Liang Wang [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=a161d0b60902062345u5d787babyb1c6385c262a3833@mail.gmail.com \
--to=netcasper@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jon@jrock.us \
/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).