DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:message-id:date:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=nFK
	1HdAiCY1divnwT+ilao8O8OJh5tvGLBVfbKtemUO4rWcIJkbTELmkoQKgmw3e6ca
	nYWwgQfPVWMH45xtl0svBQYDIg5kNoP34n/+eVQY1bQXYRBNG+IuRtxvEvZPToQQ
	BR5ZYmmtCaeICqnJtnQeNtjsB1VlonKuK+cZBVok=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
To: cygwin@cygwin.com
From: Greywolf <greywolf@starwolf.com>
Subject: XTerm 329-1 throwing error on absent bold font
Message-ID: <2be74d57-bfc7-b61f-6b89-4d1f85cfb022@starwolf.com>
Date: Tue, 20 Jun 2017 15:31:42 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Greetings,

Whenever I start up an XTerm, even if I have the resources

allowBoldFonts:	false

it throws the following error:

xterm: cannot load font "-Sun-Serif-bold-R-*-*-14-140-72-72-M-80-ISO8859-1"

Never mind the font name, this is irrelevant.  The fact that it wasn't 
throwing an error until my most recent upgrade today is bothersome.

Cygwin: 64-bit, CYGWIN_NT-10.0-WOW 2.8.0(0.309/5/3) 2017-04-01 20:42
XTerm: 329-1

Version 327-1 does not exhibit this behaviour.


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