From: Katsumi Yamaoka <yamaoka@jpl.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Make raise-frame work on Cygwin
Date: Thu, 17 May 2012 20:42:54 +0900 [thread overview]
Message-ID: <b4mlikrf2yp.fsf@jpl.org> (raw)
In-Reply-To: 4FB4C037.6060206@gmx.at
martin rudalics wrote:
>> raise-frame doesn't pop up an existing frame on Cygwin (rootless).
>> If there are many frames on a Windows screen, we have no means to
>> pop up a certain Emacs frame that is hidden by the other frames,
>> except for manually digging it up by mouse.
> Probably a silly question: What does Cygwin do to pop it up when you are
> "manually digging it up by mouse"? Or is Cygwin bypassed by Windows in
> that case?
I don't know at all. What I only do is, for instance, to type
`M-x gnus-other-frame RET' to raise an existing Gnus frame up.
`gnus-other-frame' runs `select-frame-set-input-focus' for the
Gnus frame in question, nevertheless I thereafter need to
dislodge or iconify other frames one by one by mouse till a Gnus
frame is found. :<
>> But at last I found
>> a workaround:
>>
>> (defadvice raise-frame (before make-it-work (&optional frame) activate)
>> "Make it work on Cygwin."
>> (when frame (make-frame-invisible frame)))
>> iconify-frame instead of make-frame-invisible there has no effect.
> Dead-ugly. Nevertheless, we should provide support for that, e.g., by
> introducing a `raise-frame-function' variable.
What I really want is to improve Emacs so as to communicate with
common window managers, including that of Windows 7, metacity...
Though all window managers may perhaps not offer the complete set
of interface.
next prev parent reply other threads:[~2012-05-17 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 23:44 Make raise-frame work on Cygwin Katsumi Yamaoka
2012-05-17 6:59 ` Katsumi Yamaoka
2012-05-17 11:42 ` Katsumi Yamaoka
2012-05-17 12:37 ` martin rudalics
2012-05-17 9:09 ` martin rudalics
2012-05-17 11:30 ` Achim Gratz
2012-05-17 12:37 ` martin rudalics
2012-05-17 11:42 ` Katsumi Yamaoka [this message]
2012-05-17 12:37 ` martin rudalics
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=b4mlikrf2yp.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).