unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Greg Stark <gsstark@mit.edu>
Cc: Stefan Monnier <monnier+gnu.emacs.bug/news/@rum.cs.yale.edu>
Subject: Re: Frames getting raised all the time
Date: 09 May 2003 10:52:35 -0400	[thread overview]
Message-ID: <87of2c6uks.fsf@stark.dyndns.tv> (raw)
In-Reply-To: <200303271650.h2RGotNl028733@rum.cs.yale.edu>


"Stefan Monnier" <monnier+gnu.emacs.bug/news/@rum.cs.yale.edu> writes:

> > Sure, but what if I *wanted* that frame partially hidden by something? Why
> > would this logic not apply to every other application? Should mozilla raise
> > it's windows every time a web page loads because there might be another
> > mozilla window obscuring it? Should xterm raise its window every time there's
> > terminal output in case there's another xterm on top?

Hm, perhaps this is relevant? It appears there's an ICCCM way for an
application to tell the window manager that a window is "urgent" and then
leave it for the window manager to decide what to do with this information:

http://lists.eazel.com/pipermail/sawfish/2001-January/000244.html


> I actually think the problem you describe is indeed a bug and is due to
> the fact that selected_frame is temporarily changed to the minibuffer frame,
> so Emacs doesn't realize that the frame from which you hit C-x C-f
> is actually the same as the one it's trying to make visible.
> 
> The patch below fixes your simple test case.


Is this patch in 21.3 ?

-- 
greg

       reply	other threads:[~2003-05-09 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200303271650.h2RGotNl028733@rum.cs.yale.edu>
2003-05-09 14:52 ` Greg Stark [this message]
2003-03-26  6:09 Frames getting raised all the time Gregory Stark
2003-03-27  3:30 ` Richard Stallman
2003-03-27  4:17   ` Greg Stark

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=87of2c6uks.fsf@stark.dyndns.tv \
    --to=gsstark@mit.edu \
    --cc=monnier+gnu.emacs.bug/news/@rum.cs.yale.edu \
    /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).