public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Kiehl, Horst" <h.p.kiehl@fz-juelich.de>
To: "cygwin-xfree@cygwin.com" <cygwin-xfree@cygwin.com>
Subject: RE: Why does nedit complain about these missing fonts?
Date: Mon, 21 May 2012 15:30:00 -0000	[thread overview]
Message-ID: <4094A9D4E3EC2544B795DFEA610AE88C18173D691B@IBT040.ibt-w2k.kfa-juelich.de> (raw)
In-Reply-To: <1337611301.11645.140661078548101.2F879C98@webmail.messagingengine.com>

[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]

Ronald Fischer wrote [text rewrapped]:

> So I run setup again to install the required fonts, and also (via
> xset) did a refresh of the font path. The problem still persisted.
> Looking at the installed fonts, I found my fonts being present only
> in /usr/share/fonts/100dpi and /usr/share/fonts/75dpi as a bunch of
> gz-files. I'm not sure whether this is correct (i.e. whether the X
> server is supposed to unpack them on demand), or whether the Cygwin
> setup script is supposed to do this. I think it is the latter,
> because when I did a
> 
>   xset fp+ /usr/share/fonts
> 
> I got the error message
> 
> xset:  bad font path element (#90), possible causes are:
>     Directory does not exist or has wrong permissions
>     Directory missing fonts.dir
>     Incorrect font server address or syntax

My guess is that you get this message because the directories in the
font path are from the viewpoint of the server. If your Xming
installation is on the same computer as your Cygwin installation and
the latter is under C:\cygwin, your command
    xset fp+ /usr/share/fonts
would translate to something like
    xset fp+ c:/cygwin/usr/share/fonts
The actual format expected by Xming might differ; see the output of
    xset q
for its font path. You might need to experiment a little.

Additionally, if I remember correctly, each directory containing a
fonts.dir file must be specified in the font path explicitly (i.e. the
directories in the font path are not searched recursively). So the
font path extension you need is possibly rather something like
    xset fp+ c:/cygwin/usr/share/fonts/75dpi,c:/cygwin/usr/share/fonts/100dpi

Horst

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5734 bytes --]

  reply	other threads:[~2012-05-21 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 12:43 Ronald Fischer
2012-05-18 18:37 ` Yaakov (Cygwin/X)
2012-05-19 10:20   ` Ronald Fischer
2012-05-20  4:18     ` Yaakov (Cygwin/X)
2012-05-20 10:07       ` Ronald Fischer
2012-05-20 19:19         ` Yaakov (Cygwin/X)
2012-05-21 14:42           ` Ronald Fischer
2012-05-21 15:30             ` Kiehl, Horst [this message]
2012-05-22  7:04               ` [SOLVED] " Ronald of Steiermark
2012-05-21 14:49           ` Ronald Fischer

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=4094A9D4E3EC2544B795DFEA610AE88C18173D691B@IBT040.ibt-w2k.kfa-juelich.de \
    --to=h.p.kiehl@fz-juelich.de \
    --cc=cygwin-xfree@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).