public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Font problems in cygwinx
Date: Sat, 3 Jul 2021 11:53:43 -0400	[thread overview]
Message-ID: <a15d2a3d-05a2-152d-5a15-db8cda7b078c@cornell.edu> (raw)
In-Reply-To: <069f7d28-46fa-564d-aced-f656765eee09@bellsouth.net>

On 7/3/2021 12:28 AM, Robert McBroom wrote:
> On 7/2/21 5:46 PM, Ken Brown via Cygwin wrote:
>> On 7/2/2021 5:21 PM, mcforum wrote:
>>> The legends in the heading for emacs have turned into boxes. the text in 
>>> buffers is normal.
>>
>> I'm not sure what you mean by "legends in the heading".  And when you say 
>> "have turned into boxes", are you saying that the problem just recently 
>> started?  Or have you always found X11 emacs unusable?
>>
> The labels on the drop down menus and their contents. Been using emacs on cygwin 
> for decades.

So you're saying this is a recent problem?  Can you think of anything on your 
system that has changed since X11 emacs was last usable for you?

>>> What interaction is causing this? The X11 emacs is unusable emacs -w32 works.
>>
>> My best guess is that the problem is caused by your customizations. What 
>> happens if you run 'emacs -Q'?
> Don't do customizations. -Q doesn't help

You said in a different message that you use Courier New.  How are you selecting 
the font in emacs?  And does the problem still occur if you just let emacs 
choose the font?

>> If you still see the problem with 'emacs -Q', please give a more detailed bug 
>> report, following the guidelines here:
>>
>>   https://cygwin.com/problems.html
>>
>> And please say exactly how you're starting emacs.
> 
> cygwin terminal-->startxwin-->cygwin terminal
> 
> emacs . -fh -geometry 100-512 &

Once again, please follow the problem-reporting guidelines at

   https://cygwin.com/problems.html

Ken

  reply	other threads:[~2021-07-03 15:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <537310537.2884061.1625260886292.ref@mail.yahoo.com>
2021-07-02 21:21 ` mcforum
2021-07-02 21:46   ` Ken Brown
2021-07-03  4:28     ` Robert McBroom
2021-07-03 15:53       ` Ken Brown [this message]
2021-07-02 21:58   ` Brian Inglis
2021-07-03  4:33     ` Robert McBroom
2021-07-03 16:41       ` Brian Inglis

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=a15d2a3d-05a2-152d-5a15-db8cda7b078c@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).