From: Tom Szczesny <tavmem@gmail.com>
To: cygwin@cygwin.com
Subject: Xemacs: Adding a Font
Date: Tue, 07 Aug 2012 00:15:00 -0000 [thread overview]
Message-ID: <CABn7SNY3L6OpygH1X6ts10rdsS5YeVjarmdXhmPFY_w64vgfgw@mail.gmail.com> (raw)
Thanks Mark (for the Cygwin/X suggestions).
I went the X-route in Cygwin only because that is what I did in Gentoo.
But Xemacs works perfectly well in Cygwin w/o starting an X-server.
So, the X-server appears to be a needless step.
However, the fonts displayed by Xemacs (when not using X-server)
are quite different than the fonts (with X-server).
I suspect that the fonts (when not using X-server) are stored in a
completely different place.
(not in /usr/share/fonts/misc)
Where does Xemacs get its fonts (when not using X-server)?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2012-08-06 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 0:15 Tom Szczesny [this message]
2012-08-07 2:22 ` Tom Szczesny
-- strict thread matches above, loose matches on Subject: below --
2012-08-06 4:30 Xemacs: Adding a font Tom Szczesny
2012-08-06 8:16 ` Mark Geisert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABn7SNY3L6OpygH1X6ts10rdsS5YeVjarmdXhmPFY_w64vgfgw@mail.gmail.com \
--to=tavmem@gmail.com \
--cc=cygwin@cygwin.com \
/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).