unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Mick Bert <micbert75@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Face customisation ignored
Date: Fri, 14 Sep 2018 08:59:00 +0200	[thread overview]
Message-ID: <CACE4N+VLwaSt-VFqsyXmfLM-WqeTpxfHUzyJisWs+7xdJQpdvw@mail.gmail.com> (raw)
In-Reply-To: <pnamdq$27d$1@gioia.aioe.org>

Il giorno mer 12 set 2018 alle ore 11:36 Javier
<invalid@invalid.invalid> ha scritto:
>
> Using emacs*reverseVideo might not be a good idea.
> Try setting background and foreground explicitly.
> For testing you can put the resources in the command line.
>
> emacs \
>     -xrm 'emacs*background:   #404040' \
>     -xrm 'emacs*foreground:   #0099FF'
>
>
Thanks for suggestion.
I eventualy obtain the desired behavior by specifying all the face
details (included background color) in the .emacs configuration file.

> Also, if you are using .Xresources you may want to try emacs compiled
> with the lucid toolkit instead of GTK.  Some of the .Xresources
> values do not work with GTK.  You should have a package
> emacs-lucid or emacs24-lucid in your distro.

I usually prefer the lucid version of emacs, but it's not in the
repository my company set up for the machine I use (it's a mirror
RHEL, containing just a sub-set of the packages). Even emacs itself
was just a special concession.

I am still curious to undersand why  the two ways of starting the
server behaves in different ways, but it's not critical.
I mean, always starting from a clean context (that is without any
running server),

  emacs

reades the resources, while

  emacsclient --create-frame --alternate-editor=emacs

does not

--
Mick



  reply	other threads:[~2018-09-14  6:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.663.1536735420.1284.help-gnu-emacs@gnu.org>
2018-09-12  9:31 ` Face customisation ignored Javier
2018-09-14  6:59   ` Mick Bert [this message]
     [not found]   ` <mailman.764.1536908361.1284.help-gnu-emacs@gnu.org>
2018-09-15 15:30     ` Javier
2018-09-24 12:32       ` Mick Bert
2018-09-12  6:56 Mick Bert

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=CACE4N+VLwaSt-VFqsyXmfLM-WqeTpxfHUzyJisWs+7xdJQpdvw@mail.gmail.com \
    --to=micbert75@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).