X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:message-id:in-reply-to:subject :mime-version:content-type:content-transfer-encoding; q=dns; s= default; b=ViVHgcXz0RrrNYMbrrkZlnYtQdI9I59CcdHKU7kOKUMzLlUipdVhx wZ9P+ZYeFQNfggmNEa2dE17Q1Nv7K9+xhzYxfp9xy0fymarUGkKZ/hjBBZ5rNMQY 5D4cH0PnsXsAM0dZ1q+OS8RhfIFNQxZmO1AFSieLW5Ekc9jBh5XjRI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:cc:message-id:in-reply-to:subject :mime-version:content-type:content-transfer-encoding; s=default; bh=F4ll1fneSe/t6ro3mwMetPxydo0=; b=pFZQrn8Z1B+PnIvA8A6eeBx2W/YS JvWE12tO2cQyZAvIBu/ZjGbZ005AZm5Qv3jLL8Z0HOf0Ldion1JI1WDIISbhjvaB X/GJ/z5DZBoqIV09NswKgzjUxXg1ri0Kwd5ksrw52iI8hdLlcXyrGOsdDkw65VF1 dVRO21LttZi4X/E= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,RCVD_IN_DNSWL_LOW,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=H*UA:FF3.0, greywolf, H*x:FF3.0, Greywolf X-HELO: smtp-nf-201.his.com X-ASG-Debug-ID: 1498033289-061c414ee518c40001-w5GHUG X-Barracuda-Envelope-From: dickey AT his DOT com X-Barracuda-RBL-Trusted-Forwarder: 216.194.196.20 X-Barracuda-RBL-Trusted-Forwarder: 216.194.248.141 Date: Wed, 21 Jun 2017 04:21:20 -0400 (EDT) X-Barracuda-RBL-Trusted-Forwarder: 216.194.248.141 From: Thomas Dickey To: Greywolf Cc: cygwin AT cygwin DOT com Message-ID: <284622576.4371901.1498033280666.JavaMail.root@his.com> In-Reply-To: <2be74d57-bfc7-b61f-6b89-4d1f85cfb022@starwolf.com> Subject: Re: XTerm 329-1 throwing error on absent bold font MIME-Version: 1.0 X-ASG-Orig-Subj: Re: XTerm 329-1 throwing error on absent bold font Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Barracuda-Connect: smtp-nf-202.his.com[216.194.196.20] X-Barracuda-Start-Time: 1498033289 X-Barracuda-URL: https://spam.his.com:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 915 X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.40043 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- ----- Original Message ----- | From: "Greywolf" | To: cygwin AT cygwin DOT com | Sent: Tuesday, June 20, 2017 6:31:42 PM | Subject: XTerm 329-1 throwing error on absent bold font | | 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. see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219800 -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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