From: Peter Dyballa <Peter_Dyballa@web.de>
To: Andrew Michael Levin <andrew.m.levin@vanderbilt.edu>
Cc: help-gnu-emacs Help <help-gnu-emacs@gnu.org>
Subject: Re: using emacs with nx
Date: Mon, 29 Jul 2013 17:11:54 +0200 [thread overview]
Message-ID: <77681328-1077-406D-8962-43FA6A41BDBB@web.de> (raw)
In-Reply-To: <CA+6A3sELfj1qG4ujJQJ+hf_74DiPiW4Ps3wWeoaMuKQhsBFNig@mail.gmail.com>
Am 29.07.2013 um 15:35 schrieb Andrew Michael Levin:
> My laptop is running windows. I don't know what or where xfontsel,
> xlsfonts, or libfontconfig are. How can I check these things?
These things are UNIX things. They get installed when you install X Windows or X11 (https://en.wikipedia.org/wiki/X_Window_System).
>
> Is there a way to make emacs not use these fonts?
Find at least one tool that can tell you which fonts are available in that "nx" environment. Then choose something useful from this set and make GNU Emacs use fonts from this set. If the Emacs running natively in MS and that in the "nx" environment are using the same init file, then you can check whether these Emacsen see that they are running in either this or that environment. If this works you can optimise the init file to make GNU Emacs use optimised (font) settings for this or that environment.
In X11 X resources are set up to tell GNU Emacs and other X clients which fonts, colours, geometries, etc. to use. On non-UNIX platforms maybe GNU Emacs is also reading the file .Xresources or .Xdefaults, if it exists in the HOME directory. The contents of these files can be, for example:
Emacs.font: Lucida Sans Typewriter:autohint=true:antialias=true:style=Regular:size=7
Emacs.menu*.font: Vera Humana 95:style=Bold:size=7
Emacs.pane.menubar.font: Libris ADF Std:size=7:autohint=true:antialias=true:style=Bold
Emacs.pane.menubar.*.fontList: -*-luxi sans-bold-r-normal-*-*-60-*-*-*-*-iso10646-1
Emacs.pane.menubar.popup_*.*.fontList: -*-new century schoolbook-bold-r-normal-*-*-70-*-*-*-*-iso10646-1
Emacs.menu*.fontList: -*-utopia-bold-r-*-*-*-55-*-*-*-*-iso10646-1
Emacs.dialog*.font: -*-lucidatypewriter-bold-r-*-sans-6-*-*-*-*-*-iso10646-1
Emacs.dialog*.font: Lucida Sans Typewriter:autohint=true:antialias=true:style=Regular:size=7
Emacs.dialog*background: RosyBrown4
Emacs.dialog*foreground: SpringGreen3
(The font names containing the element "-*" are those delivered by the X server, the others are served by libfontconfig.)
If it does not read these files, then it's possible to launch GNU Emacs with arguments that "artificially" set X resource values: emacs -xrm 'Emacs.menu*.font: Vera Humana 95:style=Bold:size=7'. Or how ever this can be done in MS or "nx" environments!
--
Greetings
Pete
Wasting time is an important part of living.
next prev parent reply other threads:[~2013-07-29 15:11 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
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 [this message]
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=77681328-1077-406D-8962-43FA6A41BDBB@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).