From: martin rudalics <rudalics@gmx.at>
To: "Óscar Fuentes" <ofv@wanadoo.es>, 38143@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: Sat, 9 Nov 2019 10:01:34 +0100 [thread overview]
Message-ID: <db7c4068-42fd-e903-be83-4992984ed51d@gmx.at> (raw)
In-Reply-To: <87mud5ivou.fsf@telefonica.net>
> Currently de docstrings of those variables do not mention that they are
> not invoked for the initial frame. Adding that detail is trivial, except
> that when the initial frame belongs to a daemon they are invoked.
>
> I'm not sure how to word that information.
The reason is that the initial frame is not made by 'make-frame'. The
Elisp manual says
Note that any functions added to these hooks by your initial file are
usually not run for the initial frame, since Emacs reads the initial
file only after creating that frame. However, if the initial frame is
specified to use a separate minibuffer frame (*note Minibuffers and
Frames::), the functions will be run for both, the minibuffer-less and
the minibuffer frame.
This explanation is slightly misleading: Since the initial frame is
not created by 'make-frame', Emacs would not run these hooks even if
it did read the initial file earlier. Hints for improving the
documentation are welcome.
martin
next prev parent reply other threads:[~2019-11-09 9:01 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 [this message]
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
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
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=db7c4068-42fd-e903-be83-4992984ed51d@gmx.at \
--to=rudalics@gmx.at \
--cc=38143@debbugs.gnu.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 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).