From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin@cygwin.com
Cc: mike@kmcardiff.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 18:10:00 -0000 [thread overview]
Message-ID: <56140E93.6060109@dronecode.org.uk> (raw)
In-Reply-To: <5613FCEB.30603@cornell.edu>
On 06/10/2015 17:55, Ken Brown wrote:
> On 10/6/2015 12:43 PM, Michael Enright wrote:
>> On Tue, Oct 6, 2015 at 7:42 AM, kuaf wrote:
>>> Unable to extract
>>> /etc/X11/fontpath.d/xorg-x11-fonts-75dpi:unscaled:pri=20
>>
>> Something tells me that this error message is not only giving a file
>> name, it is giving some font parameters that had been specified
>> directly or indirectly by the application. The colons divide the
>> string into parameters and the first one is a file or directory.
>
> No, it's a file name. See my earlier replies in this thread.
It is a filename.
It has certain attributes about how the X server should use that
fontpath element encoded into the symlink filename.
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
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
--
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 prev parent reply other threads:[~2015-10-06 18:10 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 [this message]
2015-10-06 23:40 ` Michael Enright
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=56140E93.6060109@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=mike@kmcardiff.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).