From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: larsi@gnus.org, 38143-done@debbugs.gnu.org
Subject: bug#38143: 27.0.50; Say that before-make-frame-hook & after-make-frame-functions are not invoked for the initial frame
Date: Tue, 07 Dec 2021 19:58:33 +0200 [thread overview]
Message-ID: <83r1aoxpo6.fsf@gnu.org> (raw)
In-Reply-To: <871r2pb9o5.fsf@telefonica.net> (message from Óscar Fuentes on Tue, 07 Dec 2021 00:22:50 +0100)
> From: Óscar Fuentes <ofv@wanadoo.es>
> Cc: Eli Zaretskii <eliz@gnu.org>, rudalics@gmx.at, 38143@debbugs.gnu.org
> Date: Tue, 07 Dec 2021 00:22:50 +0100
>
> > I think we need some input from the bug reported about what they meant
> > by "initial frame" here.
>
> I just tested with master and, indeed, the hook is executed. However, to
> be effective for all invocations of make-frame the user must add the
> function early enough (which means `early-init.el`.) When emacs.el is
> processed it is too late as the initial frame (the frame created by
> simply invoking emacs without parameters) already exists.
>
> Maybe we could expand the docstrings of the hooks and/or make-frame to
> note that you need early-init.el if you want your hooks executed when
> the initial frame is created.
>
> Otherwise, this bug can remain closed.
Done and done.
Thanks.
next prev parent reply other threads:[~2021-12-07 17:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 3:18 bug#38143: 27.0.50; Say that before-make-frame-hook & after-make-frame-functions are not invoked for the initial frame Óscar Fuentes
2019-11-09 9:01 ` martin rudalics
2019-11-09 9:27 ` Eli Zaretskii
2019-11-09 17:21 ` Óscar Fuentes
2021-12-05 3:13 ` Lars Ingebrigtsen
2021-12-05 9:47 ` Eli Zaretskii
2021-12-05 20:17 ` Lars Ingebrigtsen
2021-12-05 20:21 ` Eli Zaretskii
2021-12-06 23:22 ` Óscar Fuentes
2021-12-07 17:58 ` Eli Zaretskii [this message]
2019-11-10 9:45 ` martin rudalics
2019-11-14 9:46 ` Eli Zaretskii
2019-11-14 9:59 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r1aoxpo6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38143-done@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=ofv@wanadoo.es \
/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.