unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Andrew Michael Levin <andrew.m.levin@vanderbilt.edu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: using emacs with nx
Date: Mon, 10 Jun 2013 13:14:35 +0200	[thread overview]
Message-ID: <A09EA0A0-DD81-4502-9A81-078C7C6B54F9@Web.DE> (raw)
In-Reply-To: <CA+6A3sEHN+8Gt792NxeF7jzgX1GzinB2UifYGkhOKjKfyXhpUg@mail.gmail.com>


Am 10.06.2013 um 09:34 schrieb Andrew Michael Levin:

> These warnings do not occur when I use emacs directly on the machine the
> same machine (i.e. not using nx).
> 
> What can I add to my .emacs file to avoid these errors?

Presumingly nothing. Although I don't understand what this "nx" is, the *Warnings* mean that the X server which manages to display your GNU Emacs instance does not seem to find these two fonts. This has to do with the X server's font path, retrieved by 'xset -q'. Just make sure that the responsible X server find its fonts – or set up a (local?) font server!

Modern Emacsen seem to prefer Xft rendered fonts from the libfontconfig based fonts service. These fonts have simpler names, for example 'Lucida Sans Typewriter:autohint=true:antialias=true:size=8', so I wouldn't care about these  *Warnings*.

--
Greetings

  Pete

"When you breath, you inspire. When you do not breath, you expire."




  reply	other threads:[~2013-06-10 11:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10  7:34 using emacs with nx Andrew Michael Levin
2013-06-10 11:14 ` Peter Dyballa [this message]
2013-06-13 11:35   ` Andrew Michael Levin
2013-06-13 12:13     ` Peter Dyballa
2013-07-29 13:35       ` Andrew Michael Levin
2013-07-29 15:11         ` Peter Dyballa
2013-07-29 16:23           ` Eli Zaretskii
2013-07-30  2:28             ` Harry Putnam
2013-07-30  8:24               ` Peter Dyballa
2013-07-30 15:02                 ` Harry Putnam
2013-07-30 15:29                   ` Peter Dyballa

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=A09EA0A0-DD81-4502-9A81-078C7C6B54F9@Web.DE \
    --to=peter_dyballa@web.de \
    --cc=andrew.m.levin@vanderbilt.edu \
    --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).