Re: Understanding after-make-frame-functions

[Eli Zaretskii <eliz@gnu.org>]

> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Tue, 17 May 2016 18:08:43 +0000
> 
>  What Emacs does during startup is documented in the ELisp manual, see
>  the node "Startup Summary". If you have specific suggestions for
>  amendments there, please file a bug report with those suggestions.
> 
> I had already gone through that but it does not talk about the nuance that in daemon mode case, the frame is
> created after the window-setup-hook is run; whereas it is created before evaluating the init in the case of
> non-daemon mode. The side effect of that on after-make-frame-functions hook being useful only for daemon
> cases is also not mentioned anywhere.

When Emacs starts in daemon mode, it doesn't create any frames at all,
so I don't think I understand what you are saying here.

> I do not know what's the correct terminology to be used for "user emacs config", "daemon mode" and
> "non-daemon mode" in documentation, but the idea for after-make-frame-functions documentation is as
> below:
> 
> =====
> Functions to run after a frame is created.
> The functions are run with one arg, the newly created frame.
> 
> In daemon mode (emacs --daemon or emacsclient), the frame is created at some point after the
> `window-setup-hook' is run (after the user emacs config is evaluated). So this hook is called _after_ the user
> config evaluation.
> 
> But in the non-daemon mode, the frame is created before the user emacs config is evaluated. So this hook is
> run before that, and so any user customization done to this hook would be ineffective in the non-daemon
> case.

I think it would be clearer just to say that this hook cannot be used
for the initial frame.