public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Bruce Ingalls <bingalls@nj.rr.com>
To: cygwin-xfree@cygwin.com
Subject: display bug
Date: Mon, 08 Dec 2003 15:57:00 -0000	[thread overview]
Message-ID: <3FD49F93.9030206@nj.rr.com> (raw)

I noticed an interesting bug.
When I started emacs& from my xterm, then dragged the xterm window out 
of the way,
during the time that emacs was taking a long time to launch, the emacs 
display was being
written to both windows.
When I clicked on the title bar of the xterm, then both the emacs 
window, where it overlapped
the previous xterm position, and the current xterm position, both showed 
the xterm display.

Finally, I dragged the current emacs displaying xterm back, to align 
with its overlapping xterm
display, and X Window went back in synch.

I am running a default configuration of the latest stable version of 
cygwin-xfree (v4.3?) on
XP home. This is a rootless system.

I'm not sure how easy it will be to reproduce the problem, as the timing 
of moving the parent
xterm seems important.


                 reply	other threads:[~2003-12-08 15:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3FD49F93.9030206@nj.rr.com \
    --to=bingalls@nj.rr.com \
    --cc=cygwin-xfree@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).