From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>
Cc: 15133@debbugs.gnu.org
Subject: bug#15133: 24.3.50; REGRESSION: `after-make-frame-functions' now run with wrong frame selected
Date: Mon, 19 Aug 2013 22:07:10 +0200 [thread overview]
Message-ID: <52127AEE.8010101@gmx.at> (raw)
In-Reply-To: <391c84ad-a338-41df-96ed-287508f86d66@default>
> Sorry, I don't understand. What "both" would you like me to try? This
> needs to work as it did before the regression - both `pop-to-buffer'
> and `display-buffer'.
Did `display-buffer' work correctly?
> But first, I don't understand either why there should be any difference.
> Why shouldn't functions on `after-make-frame-functions' always be passed
> the new frame as argument, as has been the case in the past? There is a
> `before-make-frame-functions' hook for passing the originally selected
> frame.
The problem is that the new frame doesn't yet show the buffer you want
to display when `after-make-frame-functions' is called.
> Perhaps you are thinking that this is about _selecting_ the new frame?
> (I mistakenly mentioned "is selected" above, when I meant is passed to
> the hook functions.)
>
> I can understand that `pop-to-buffer' and `display-buffer' might act
> differently wrt selecting the buffer's frame. But I do not understand
> why suddenly the functions on hook `after-make-frame-functions' should
> be passed the original frame as arg instead of the new frame.
Do they really get passed the original frame?
> How else can someone invoke a function on the new frame as part of the
> process of frame creation?
Please check again.
martin
next prev parent reply other threads:[~2013-08-19 20:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 15:01 bug#15133: 24.3.50; REGRESSION: `after-make-frame-functions' now run with wrong frame selected Drew Adams
2013-08-19 15:08 ` Drew Adams
2013-08-19 16:13 ` martin rudalics
2013-08-19 18:25 ` Drew Adams
2013-08-19 20:07 ` martin rudalics [this message]
2013-08-19 21:46 ` Drew Adams
2013-08-20 7:05 ` martin rudalics
2013-08-20 15:16 ` Drew Adams
2013-08-20 17:24 ` martin rudalics
2013-08-20 18:03 ` Drew Adams
2013-08-23 7:08 ` martin rudalics
2013-08-23 7:45 ` Drew Adams
2013-08-24 2:19 ` Drew Adams
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=52127AEE.8010101@gmx.at \
--to=rudalics@gmx.at \
--cc=15133@debbugs.gnu.org \
--cc=drew.adams@oracle.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.