public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: XTerm always gives out an error message concerning a font
Date: Thu, 06 Jul 2017 20:54:00 -0000	[thread overview]
Message-ID: <fc98db96-7019-99a6-855c-7f57f2707b87@SystematicSw.ab.ca> (raw)
In-Reply-To: <CANZ2p_dZu0fpQWdHGWxmh+L416BD0h9CChD394_9JA0H=gF0Bg@mail.gmail.com>

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

  reply	other threads:[~2017-07-06 20:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 11:39 Wouter van Doorn
2017-07-06 16:45 ` Brian Inglis
2017-07-06 16:58   ` Wouter van Doorn
2017-07-06 20:54     ` Brian Inglis [this message]
2017-07-06 21:32       ` Wouter van Doorn
2017-07-12 23:52         ` Thomas Dickey

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=fc98db96-7019-99a6-855c-7f57f2707b87@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.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).