public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Michael Enright <mike@kmcardiff.com>
To: Jon Turney <jon.turney@dronecode.org.uk>
Cc: cygwin@cygwin.com
Subject: Re: Cygwin/X installation: Unable to extract /etc/X11/fontpath.d/xorg-x11-fonts-75dpi:unscaled:pri=20
Date: Tue, 06 Oct 2015 23:40:00 -0000	[thread overview]
Message-ID: <CAOC2fq-Dixr8zSE2yYPc5H2br4n7oxzAbz3hJAYN3ewMOc4dSA@mail.gmail.com> (raw)
In-Reply-To: <56140E93.6060109@dronecode.org.uk>

On Tue, Oct 6, 2015 at 11:10 AM, Jon Turney  wrote:
>
> But there is no need to guess about this, it's documented in the fontpath.d
> section of the Xserver man page [1]
>
> [1] http://x.cygwin.com/docs/man1/Xserver.1.html#lbAN
>

I still have questions.

Good old setup_x86 fortuitously gave me the chance to see an error
message involving one of these symlinks. I reviewed the setup log and
read that apparently such a symlink was created as follows:
io_stream:mklink
(cygfile:///etc/X11/fontpath.d/xorg-x11-75dpi:unscaled:pri=20 ->
cygfile:///usr/share/X11/fonts/75dpi)
But there is no /etc/X11/fontpath.d directory on the system.

The man page doesn't say in explicit procedural terms what the end
user has to do to make fontpath.d exist and it doesn't seem to get
created by setup. There are three occurances of fontpath.d on that
page and none of them say where you should put it.

Could we change it to be more tutorial, something like:
If you wanted to modify the priority of the bitmap fonts for example,
you could go to /etc/X11 and create fontpath.d and then here are some
ln commands:
ln -s /usr/share/X11/fonts/75dpi xorg-x11-75dpi:unscaled:pri=20
...

--
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

  reply	other threads:[~2015-10-06 23:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 14:42 kuaf
2015-10-06 15:05 ` Andrey Repin
2015-10-06 15:26   ` Ken Brown
2015-10-06 15:06 ` Ken Brown
2015-10-06 16:12   ` kuaf
2015-10-06 16:43 ` Michael Enright
2015-10-06 16:55   ` Ken Brown
2015-10-06 18:10     ` Jon Turney
2015-10-06 23:40       ` Michael Enright [this message]
2015-10-07  0:05         ` Andrey Repin
2015-10-07  0:22         ` Ken Brown
2015-10-12 23:49           ` Yaakov Selkowitz

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=CAOC2fq-Dixr8zSE2yYPc5H2br4n7oxzAbz3hJAYN3ewMOc4dSA@mail.gmail.com \
    --to=mike@kmcardiff.com \
    --cc=cygwin@cygwin.com \
    --cc=jon.turney@dronecode.org.uk \
    /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).