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:reply-to:subject:references:to:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=RDCMK7uIfCmm9urx 2LeDpP8gtoxAgwSoF2YpdofLFutzq/bupZ/EZzgxiPmQcBb/MP1OK0kxGJ8KJYdT kGMgK0MeE2izgDbkhWee/nsHoMm2R821GiSVdfdg5akVOOqPY8aPyoJFoOBkLfez FByFIKDrYR0aw5FVJ8+I3Wgmk60= 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:reply-to:subject:references:to:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=8KxttpSxS6b/TFG3kMIhTp KJnV8=; b=KG+4b448wKFi0nsiv6eDe/4XQKkx7nUz+PkRbbL4i8By7rJiffpAmX 0KKgfFCOpVRNo4VBdxNfhuQm9s8bOFWJe9eaKMYjiMxE72nIJxR1xS51XilqPMEN W2Hqs37WJnrGEqWQW+f5fYrq4BeWA2afQ/0oegmT8Ch0EDiszghTA= 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=-2.0 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=van, Wouter, doorn, Doorn X-HELO: smtp-out-no.shaw.ca X-Authority-Analysis: v=2.2 cv=a+JAzQaF c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=IkcTkHD0fZMA:10 a=HiWkEfo4AAAA:8 a=M-KynEFek4OpD9skhDoA:9 a=7Zwj6sZBwVKJAoWSPKxL6X1jA+E=:19 a=QEXdDO2ut3YA:10 a=4zpMnB1xO2oA:10 a=_QplDg0m8TGAdENQf2wZ:22 Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Subject: Re: XTerm always gives out an error message concerning a font References: <70d5141f-b1c6-538c-11ab-75614280fd4a AT SystematicSw DOT ab DOT ca> To: cygwin AT cygwin DOT com From: Brian Inglis Message-ID: Date: Thu, 6 Jul 2017 14:54:36 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfFTNls0yj9OAl+LOYglAv5TjDHLZoCORulfPceUu0qbDqbl+3VGzunkM6zQYSvS4Z+X50L8V2O5MYhbWtQapH4dmJ+YUdJa0kLqI1NAPvZJIHzPy1itr d7G057l/pJ4IcO+Jk/McgZKe0uwy4oIhIUOJKxZKARfxQVagIdfpGH1LaW7BW8ZsnzPUlbTgDTJISg== X-IsSubscribed: yes On 2017-07-06 10:58, Wouter van Doorn wrote: > Thanks, Brian. Your link shows me a page that mentions problems in > xterm-327 through 329, but I have 330, so although the symptom is very > similar, it doesn't seem to be that. Try your font name resource selections with xlsfonts until you find the one you want. You may want to try: *-fixed-medium-r-normal--18-* or *-fixed-medium-r-normal--18-*-iso8859-1 and let xterm find the bold equivalent. On my system the default first match is: -misc-fixed-bold-r-normal--18-120-100-100-c-90-iso10646-1 You might also want to check out: http://invisible-island.net/xterm/xterm.faq.html#problems_fonts It's also possible that patch #330 did not totally resolve the problem in all circumstances. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada -- 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