unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Subject: NTEmacs problems with make-frame
Date: Wed, 25 May 2005 21:49:47 +0300	[thread overview]
Message-ID: <uzmujkuno.fsf@gnu.org> (raw)

For quite some time now I sometimes see an annoying problem in the
native MS-Windows (a.k.a. NTEmacs) port of the CVS Emacs: commands
that create a new frame somehow fail to display the frame.  Examples
include "C-x b FOO RET", "C-x m" with rmail-mail-new-frame set to
non-nil, etc.  What happens is that the frame is created (it appears
in the output of `frame-list'), it is not (and cannot be) displayed.
Instead, the frame that was current becomes unselected (the cursor
changes into a hollow block), and that's it.  Emacs is not stuck: if I
move the mouse out of the Emacs frame and back into it, the frame that
was selected before the offending command becomes again selected and
everything is hunky-dory (except that there's a frame that I cannot
switch to).

This problem happens in about 50% of the attempts to use the commands
that create a new frame.

I've seen this on two different machines running Windows XP, and in
several versions since last October, up to and including the latest
binary I have, which was compiled about a month ago (I didn't yet have
time to set up a MinGW build environment, so I rely on binaries built
by others).

Does anyone else see this on MS-Windows?  The only thing that is
both peculiar and common to the two machines where I have this problem
is that both of them have Active Window Tracking (a.k.a. focus follows
mouse) feature of the window manager set to ON.

Suggestions for further testing and requests for additional
information are welcome.

TIA

             reply	other threads:[~2005-05-25 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-25 18:49 Eli Zaretskii [this message]
2005-05-25 21:17 ` NTEmacs problems with make-frame Eli Zaretskii
2005-05-26  8:11 ` Juanma Barranquero
2005-06-04 22:15 ` Neil Jerram

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uzmujkuno.fsf@gnu.org \
    --to=eliz@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).