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: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= 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:to:from:subject:message-id:date:mime-version :content-type:content-transfer-encoding; s=default; bh=lIAsDekMJ dgLdQmvN3hMp08sTNE=; b=kKUtyNSy7hcYEmd4tjHJP0r/iF/FnVeb//hkaou9O TjLurJ5iRg5v0fzHE5uM3O3U/j8vHdrCjadpW/QjGLFHe2IDR+Z5BLVlZhdjXQH4 Uf8JnF3cRAUC0D63hUOzDZXnj3IoVkSPvLTXqe4wBzvC6EEbmwpTZ9hfFqCTFogQ Zc= 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=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy= X-HELO: eddie.starwolf.com To: cygwin AT cygwin DOT com From: Greywolf 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 X-IsSubscribed: yes 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