From: Javier <invalid@invalid.invalid>
To: help-gnu-emacs@gnu.org
Subject: Re: Face customisation ignored
Date: Wed, 12 Sep 2018 09:31:38 +0000 (UTC) [thread overview]
Message-ID: <pnamdq$27d$1@gioia.aioe.org> (raw)
In-Reply-To: mailman.663.1536735420.1284.help-gnu-emacs@gnu.org
Mick Bert <micbert75@gmail.com> wrote:
>
> and a chunk of my .Xresources
>
> emacs*cursorBlibk: true
> emacs*cursorColor: #404040
> emacs*font: -*-fixed-*-r-*-*-10-*-*-*-*-*-*-*
> !emacs*font: -*-terminus-medium-*-*-*-14-*-*-*-*-*-iso8859-1
> !emacs*font: -*-nimbus mono
> l-medium-r-normal--0-0-*-*-*-*-iso8859-1
> emacs*foreground: #404040
> emacs*geometry: 140x80
> emacs*reverseVideo: true
> emacs*toolBar: true
> emacs*fullscreen: false
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'
emacsclient does not accept the xrm option, I guess because
the Xresources are loaded only once at the server initialization.
You can customize the frames created by emacsclient with
--frame-parameters=ALIST
--eval "(progn (...) (...))"
(info "(emacs) emacsclient Options")
(info "(emacs) Table of Resources")
After you edit ~/.Xresources remember to do
xrdb -merge ~/.Xresources
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.
next parent reply other threads:[~2018-09-12 9:31 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 ` Javier [this message]
2018-09-14 6:59 ` Face customisation ignored Mick Bert
[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='pnamdq$27d$1@gioia.aioe.org' \
--to=invalid@invalid.invalid \
--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).