From: Stefan Monnier <monnier@iro.umontreal.ca>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: David Reitter <david.reitter@gmail.com>,
Adrian Robert <adrian.b.robert@gmail.com>,
3303@emacsbugs.donarmstrong.com
Subject: bug#3303: delete-frame raises old (invisible) frame
Date: Tue, 19 May 2009 10:30:26 -0400 [thread overview]
Message-ID: <jwvoctpyxlk.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <wloctpo663.wl%mituharu@math.s.chiba-u.ac.jp> (YAMAMOTO Mitsuharu's message of "Tue, 19 May 2009 17:20:20 +0900")
>>> I still don't understand the above code, for the reason already
>>> explained: you use `selected-frame' in a way that seems to imply
>>> that you expect make-frame to change the selected-frame, where its
>>> docstring says explicitly that it doesn't.
>> Ah, now I see why you don't understand.
>> The doc string says that the system may select it, and that's
>> exactly what happens here on Cocoa/OSX.
> That's due to the following NS-specific code in term/ns-win.el:
> ;; frame will be focused anyway, so select it
> ;; (if this is not done, modeline is dimmed until first interaction)
> (add-hook 'after-make-frame-functions 'select-frame)
> I would read this comment as "this is a workaround". TRT is to
> investigate why the modeline is dimmed until the first interaction and
> fix it, of course. Otherwise, the NS port will face hard-to-find
> incompatibilities in various elisp packages.
Agreed. Could someone remove the above line and install a proper fix
for it?
Stefan
next prev parent reply other threads:[~2009-05-19 14:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 1:09 bug#3303: delete-frame raises old (invisible) frame David Reitter
2009-05-17 19:06 ` Stefan Monnier
2009-05-17 19:12 ` David Reitter
2009-05-17 20:43 ` Stefan Monnier
2009-05-17 22:27 ` Lennart Borgman
2009-05-18 3:26 ` Stefan Monnier
2009-05-18 1:16 ` Adrian Robert
2009-05-18 3:33 ` Stefan Monnier
2009-05-18 8:05 ` Adrian Robert
2009-05-18 15:08 ` David Reitter
2009-05-18 20:12 ` Stefan Monnier
2009-05-18 23:00 ` David Reitter
2009-05-19 2:46 ` Stefan Monnier
2009-05-19 2:56 ` David Reitter
2009-05-19 3:09 ` Stefan Monnier
2009-05-19 3:15 ` David Reitter
2009-05-19 8:20 ` YAMAMOTO Mitsuharu
2009-05-19 14:30 ` Stefan Monnier [this message]
2009-05-20 2:07 ` David Reitter
2009-05-19 0:58 ` YAMAMOTO Mitsuharu
2009-05-18 8:19 ` YAMAMOTO Mitsuharu
-- strict thread matches above, loose matches on Subject: below --
2009-05-16 19:28 Chong Yidong
2009-05-17 2:55 ` David Reitter
2009-05-22 3:57 David Reitter
2009-05-25 15:17 ` Stefan Monnier
2009-05-26 18:20 ` David Reitter
2009-05-26 19:37 ` Stefan Monnier
2009-05-26 20:15 ` David Reitter
2009-05-26 21:30 ` Stefan Monnier
2009-05-27 4:51 ` Adrian Robert
2009-05-27 14:36 ` Stefan Monnier
2009-06-01 9:37 ` Adrian Robert
2009-05-27 15:28 ` David Reitter
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=jwvoctpyxlk.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=3303@emacsbugs.donarmstrong.com \
--cc=adrian.b.robert@gmail.com \
--cc=david.reitter@gmail.com \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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).